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 steve.dower
Recipients Tony Roberts, paul.moore, pitrou, steve.dower, tim.golden, zach.ware
Date 2018-06-19.15:16:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1529421393.54.0.56676864532.issue33895@psf.upfronthosting.co.za>
In-reply-to
Content
Yeah, just after posting I remembered that the blocker is the loader lock and not filesystem/arbitrary code.


Still, "I don't think" isn't sufficient to justify making the change in 3.7 or earlier. If we can show that properly working code could never have assumed the GIL, then I guess it's fine, but otherwise it's too risky.

Making the change without any deprecation period in 3.8 is fine.
History
Date User Action Args
2018-06-19 15:16:33steve.dowersetrecipients: + steve.dower, paul.moore, pitrou, tim.golden, zach.ware, Tony Roberts
2018-06-19 15:16:33steve.dowersetmessageid: <1529421393.54.0.56676864532.issue33895@psf.upfronthosting.co.za>
2018-06-19 15:16:33steve.dowerlinkissue33895 messages
2018-06-19 15:16:33steve.dowercreate