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 christian.heimes
Recipients barry, christian.heimes, grahamd
Date 2008-10-25.00:57:54
SpamBayes Score 2.2609771e-07
Marked as misclassified No
Message-id <1224896278.13.0.0556537353625.issue4200@psf.upfronthosting.co.za>
In-reply-to
Content
Ouch! We totally forgot about sub interpreters during the
reimplementation of the atexit module. 

In my opinion it's a big bug for systems like mod_python and mod_wsgi.
However it's too late to fix it for 3.0.0. Perhaps we can fix it in
3.0.1. We always knew that Python 3.0 is going to have some bugs that
can only be revealed by 3rd party code. I've added Barry to the nosy
list in order to get his opinion as release manager. 

Do you have a suggestion how the problem should be solved? I'd store the
atexit_callback information in PyInterpreterState instead of the module.
Maybe Martin's PEP 3121 could come into play to rescue us.

By the way PEP 3121 ... does the new module initialization code play
nice with multiple sub interpreters?
History
Date User Action Args
2008-10-25 00:57:58christian.heimessetrecipients: + christian.heimes, barry, grahamd
2008-10-25 00:57:58christian.heimessetmessageid: <1224896278.13.0.0556537353625.issue4200@psf.upfronthosting.co.za>
2008-10-25 00:57:56christian.heimeslinkissue4200 messages
2008-10-25 00:57:55christian.heimescreate