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 amaury.forgeotdarc, brett.cannon, eric.snow, georg.brandl, ncoghlan
Date 2012-07-29.11:28:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In trying to find a new case that wasn't already covered by the test suite, I found an error which I'm not even sure should be an error. Doesn't 3.2 suppress failures that occur when attempting to implicitly cache the .pyc?

Anyway, given the rest of the patch, trimming this traceback will be easy if we decide that's the right thing to do.
Date User Action Args
2012-07-29 11:28:02ncoghlansetrecipients: + ncoghlan, brett.cannon, georg.brandl, amaury.forgeotdarc, eric.snow
2012-07-29 11:28:02ncoghlansetmessageid: <>
2012-07-29 11:28:01ncoghlanlinkissue15486 messages
2012-07-29 11:28:01ncoghlancreate