Nick Coghlan added the comment: 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) ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue15486> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
