David Lyon wrote: > Glen wrote: > >> So let's further say that the .zip file was named .py, instead, but was >> a .zip internally. > > The only one thing I have to say about that is that it makes > embedding of .py files recursive.
No it doesn't. The mechanisms involved for processing the top-level zipfile and those for processing the .py text files within that zipfile are completely different. > So, it begs the question "How many times can you embed a .py > within a .py?" Zipfiles inside the outermost zipfile will be ignored no matter what you call them. > And then; "How do you check if a .py is a .py?" The same way the interpreter does: try treating it as a sys.path entry and see if it works. If it does, it's a zipfile or directory (you can tell which based on the importer object you get back). If it doesn't, it's probably a script. > Whereas, if you just associate to a .egg or a .eag or some > other extension suffix, it just keeps things very orthodox > and you can have a visual queue (for users with gui- > interfaces). Python applications should have an icon based on the specific application, not one based on the implementation language the author happened to use. Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia --------------------------------------------------------------- _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
