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 belopolsky, brett.cannon, christian.heimes, eric.snow, facundobatista, georg.brandl, ncoghlan, stocker81
Date 2012-08-24.08:13:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1345796022.32.0.807750153979.issue2051@psf.upfronthosting.co.za>
In-reply-to
Content
I have a patch that works, and that I think may point the way to a replacement API for set_data in 3.4. Just running the full test suite before I check it in.

The test you posted definitely saved me a lot of time.

My version bypasses the cache, though. This isn't a disaster, since the main reason the cache is there is to speed up *failing* stat calls - this new one only incurs the hit when actually writing the bytecode file to disk, which should be lost in the noise of the actual IO write operation.

However, suggestions for improvement always welcome :)
History
Date User Action Args
2012-08-24 08:13:42ncoghlansetrecipients: + ncoghlan, brett.cannon, georg.brandl, facundobatista, belopolsky, christian.heimes, stocker81, eric.snow
2012-08-24 08:13:42ncoghlansetmessageid: <1345796022.32.0.807750153979.issue2051@psf.upfronthosting.co.za>
2012-08-24 08:13:41ncoghlanlinkissue2051 messages
2012-08-24 08:13:41ncoghlancreate