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 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 <>
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:13ncoghlansetrecipients: + ncoghlan, brett.cannon, georg.brandl, amaury.forgeotdarc, pitrou, Arfrever, meador.inge, chris.jerdonek, eric.snow
2012-07-30 01:28:13ncoghlansetmessageid: <>
2012-07-30 01:28:12ncoghlanlinkissue15486 messages
2012-07-30 01:28:12ncoghlancreate