On Sun, Feb 28, 2010 at 12:45, Baptiste Carvello <baptiste...@free.fr>wrote:
> Nick Coghlan a écrit : > > >> Another option is to remove bytecode-only support from the default >> filesystem importer, but keep it for zipimport (since the stat call >> savings don't apply in the latter case). >> >> > bytecode-only in a zip is used by py2exe, cx_freeze and the like, for space > reasons. Disabling it would probably hurt them. > > However, making a difference between zipimport and the filesystem importer > means the application will stop working if I unzip the library zip file, > which is surprising. Unzipping the zip file can be handy when debugging a > bug caused by a forgotten module. > > Is it really that hard to unzip a bunch of .pyc files, modify what you need to, and then zip it back up? And if you are given a zip file of only .pyc files you can't really debug anything anyway. -Brett > Cheers, > Baptiste > > > _______________________________________________ > 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/brett%40python.org >
_______________________________________________ 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
