Message168611
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. |
|
Date |
User |
Action |
Args |
2012-08-20 01:27:54 | ncoghlan | set | recipients:
+ ncoghlan, barry, amaury.forgeotdarc, pitrou, eric.araujo, brian.curtin, pdsimanyi, markon, mucisland, Steve.Thompson, desolat, kevin.chen |
2012-08-20 01:27:54 | ncoghlan | set | messageid: <1345426074.69.0.0641241458573.issue6074@psf.upfronthosting.co.za> |
2012-08-20 01:27:33 | ncoghlan | link | issue6074 messages |
2012-08-20 01:27:33 | ncoghlan | create | |
|