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 lemburg
Recipients amaury.forgeotdarc, benjamin.peterson, lemburg, pitrou
Date 2013-04-15.11:20:45
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1366024845.41.0.949762436964.issue17703@psf.upfronthosting.co.za>
In-reply-to
Content
Checked the patch: it fixes the problem. Thanks.

Will this go into Python 2.7.5 ?

I'm asking because we need to issue a patch level release of egenix-mx-base and if Python 2.7.5 will fix the problem, we'll just add the work-around for Python 2.7.4.

Regarding a better cleanup logic: This is available in Python 3.x with the new module init logic and we'll use it there.

PS: The approach with doing the cleanup at module startup time won't work, because the still existing objects will reference parts of the already cleaned up interpreter instance.
History
Date User Action Args
2013-04-15 11:20:45lemburgsetrecipients: + lemburg, amaury.forgeotdarc, pitrou, benjamin.peterson
2013-04-15 11:20:45lemburgsetmessageid: <1366024845.41.0.949762436964.issue17703@psf.upfronthosting.co.za>
2013-04-15 11:20:45lemburglinkissue17703 messages
2013-04-15 11:20:45lemburgcreate