At 01:08 AM 1/27/2010 -0800, Glenn Linderman wrote:
Of course, if you want to create a ZIP named .py package that is an application installer, you could do that, too. It might be handy for the case where not everything in the application can be a .py, .pyc, or .pyo... shared libraries cannot be run from the ZIP files as a documented limitation, it seems... so if those are needed, then an installer is needed too.
Or you just include a .egg subdirectory in the zipfile (using easy_install --always-unzip), and throw the pkg_resources module in the root of the zipfile. The shared libraries are then transparently unzipped to a cache directory at import time.
_______________________________________________ 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
