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 brett.cannon
Recipients brett.cannon, gregory.p.smith, twouters
Date 2015-03-20.18:14:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1426875282.27.0.254210392532.issue23723@psf.upfronthosting.co.za>
In-reply-to
Content
In environments where bytecode generation is thoroughly controlled, it would be nice if there was a way to specify that the bytecode file is externally guaranteed to be up-to-date, and thus skip any stat call involving bytecode verification. Could be represented with a timestamp of either all zeroes or ones in the bytecode file header.
History
Date User Action Args
2015-03-20 18:14:42brett.cannonsetrecipients: + brett.cannon, twouters, gregory.p.smith
2015-03-20 18:14:42brett.cannonsetmessageid: <1426875282.27.0.254210392532.issue23723@psf.upfronthosting.co.za>
2015-03-20 18:14:42brett.cannonlinkissue23723 messages
2015-03-20 18:14:42brett.cannoncreate