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.11:06:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1343646394.44.0.76243470234.issue15486@psf.upfronthosting.co.za>
In-reply-to
Content
OK, after a bit of experimentation, it appears both 3.2 and 3.3 eventually get annoyed if you mess about too much with __pycache__.

1. They're both fine if __pycache__ is entirely unwritable (they just silently skip caching the bytecode)

2. 3.2 throws EOFError if you replace the cache entry with an empty file, 3.3 silently rewrites it with a valid cached version

3. 3.2 throws EOFError if you replace the cache entry with a directory, 3.3 throws a more accurate IsADirectory error

That means my chosen test case is a valid one, and I can just update the offending call in importlib._bootrap to use the new frame stripping hook as I originally planned.
History
Date User Action Args
2012-07-30 11:06:34ncoghlansetrecipients: + ncoghlan, brett.cannon, georg.brandl, amaury.forgeotdarc, pitrou, Arfrever, meador.inge, chris.jerdonek, eric.snow
2012-07-30 11:06:34ncoghlansetmessageid: <1343646394.44.0.76243470234.issue15486@psf.upfronthosting.co.za>
2012-07-30 11:06:33ncoghlanlinkissue15486 messages
2012-07-30 11:06:33ncoghlancreate