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 ncoghlan
Recipients Steve.Thompson, amaury.forgeotdarc, barry, brian.curtin, desolat, eric.araujo, kevin.chen, markon, mucisland, ncoghlan, pdsimanyi, pitrou
Date 2012-08-20.01:27:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1345426074.69.0.0641241458573.issue6074@psf.upfronthosting.co.za>
In-reply-to
Content
OK, I tracked down the original reason for the behavioural change: #2051

The important aspect in that patch is preserving the *read* permissions from the .py file so we don't accidentally expose data to other users.

Kevin's patch seems like a good approach for restoring compatibility in 2.7 and 3.2

In 3.3, it appears that #2051 has regressed, since no test was added to confirm the correct behaviour and importlib appears to behave more like 2.5.
History
Date User Action Args
2012-08-20 01:27:54ncoghlansetrecipients: + ncoghlan, barry, amaury.forgeotdarc, pitrou, eric.araujo, brian.curtin, pdsimanyi, markon, mucisland, Steve.Thompson, desolat, kevin.chen
2012-08-20 01:27:54ncoghlansetmessageid: <1345426074.69.0.0641241458573.issue6074@psf.upfronthosting.co.za>
2012-08-20 01:27:33ncoghlanlinkissue6074 messages
2012-08-20 01:27:33ncoghlancreate