This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author jvr
Date 2003-02-25.17:20:18
SpamBayes Score
Marked as misclassified
Logged In: YES 

Here's an issue with the patch I just ran into: it seems this patch causes the first Python module to be imported to be instead of This means doesn't have full control of the import mechanism anymore, as all modules loaded by will already be loaded. Can't the PyModule_WarningsModule global be set _after_ has run?

Use case: I'm building standalone applications in which the import bootstrapping happens in a custom, assuming it will be the first Python module that will be imported. It sets up sys.path appropriately. Now it turns out that when my gets run (eg.) is already loaded from my system-wide installation, instead of from the zip file embedded in the application. This means I can't reliably test whether my built app really works when there's no Python installation available.
Date User Action Args
2007-08-23 14:10:58adminlinkissue683658 messages
2007-08-23 14:10:58admincreate