Nick Coghlan wrote:
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).
+1 Baptiste Carvello wrote:
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.
If the ZIP contains only bytecode files, it is just not intended for changing any code, so I don't think this is an argument. If you have access to the source code, you still can use that instead of messing around with byte code. Henning _______________________________________________ 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
