Message166846
| Author |
ncoghlan |
| Recipients |
Arfrever, amaury.forgeotdarc, brett.cannon, chris.jerdonek, eric.snow, georg.brandl, meador.inge, ncoghlan, pitrou |
| Date |
2012年07月30日.01:28:12 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1343611693.5.0.658620582148.issue15486@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
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) |
|