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 Jason.Killen, christian.heimes, miss-islington, plokmijnuhby, steve.dower, taleinat
Date 2019-11-18.19:32:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1574105528.63.0.986826385828.issue38722@roundup.psfhosted.org>
In-reply-to
Content
> I hadn't realized that we'd made such a declaration WRT opening of code files in general.

It wasn't exactly a hugely publicised declaration :)

The relevant quote from PEP 578 is:

> All import and execution functionality involving code from a file will be changed to use open_code() unconditionally.

Which I admit is a big claim, and one that was not completely followed through with before 3.8.0. Calling it a "security" fix is borderline, as it isn't really a vulnerability by default, but calling it incorrect behaviour (i.e. a regular bug) is fine by me.
History
Date User Action Args
2019-11-18 19:32:08steve.dowersetrecipients: + steve.dower, taleinat, christian.heimes, Jason.Killen, miss-islington, plokmijnuhby
2019-11-18 19:32:08steve.dowersetmessageid: <1574105528.63.0.986826385828.issue38722@roundup.psfhosted.org>
2019-11-18 19:32:08steve.dowerlinkissue38722 messages
2019-11-18 19:32:08steve.dowercreate