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 vstinner
Recipients benjamin.peterson, doko, neologix, vstinner
Date 2014-07-11.22:00:17
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1405116017.74.0.849759852325.issue21963@psf.upfronthosting.co.za>
In-reply-to
Content
> The changeset 7741d0dd66ca looks good to me, Python 3 does the same thing since Python 3.2 (the new GIL).

Oh, I forgot to say that the simplest way to fix the regression is to revert this commit... As I wrote modifying the code to cleanup Python at exit is risky, and it's maybe too late to do that in Python 2.7?

The risk of regression caused by 7741d0dd66ca is maybe higher than the benefit of the enhancement? :-(
History
Date User Action Args
2014-07-11 22:00:17vstinnersetrecipients: + vstinner, doko, benjamin.peterson, neologix
2014-07-11 22:00:17vstinnersetmessageid: <1405116017.74.0.849759852325.issue21963@psf.upfronthosting.co.za>
2014-07-11 22:00:17vstinnerlinkissue21963 messages
2014-07-11 22:00:17vstinnercreate