Message166846
The "release blocker" status comes from the test case I added in order to demonstrate the ability to strip a new frame sequence without needing to modify the C code.
Currently that test (failing to write the PYC file) fails with an IsADirectory traceback that includes a lot of importlib frames.
There are two possible solutions:
- redirect the affected call through "_call_with_frames_removed" but otherwise leave the failure intact
- change it so this particular case isn't a fatal error
I need to check if failing to write the .pyc was a fatal error in 3.2 before I decide how to fix it (unless someone else remembers off the top of their head) |
|
Date |
User |
Action |
Args |
2012-07-30 01:28:13 | ncoghlan | set | recipients:
+ ncoghlan, brett.cannon, georg.brandl, amaury.forgeotdarc, pitrou, Arfrever, meador.inge, chris.jerdonek, eric.snow |
2012-07-30 01:28:13 | ncoghlan | set | messageid: <1343611693.5.0.658620582148.issue15486@psf.upfronthosting.co.za> |
2012-07-30 01:28:12 | ncoghlan | link | issue15486 messages |
2012-07-30 01:28:12 | ncoghlan | create | |
|