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 akvadrako
Recipients akvadrako, brett.cannon, eric.snow, ncoghlan
Date 2017-10-13.06:19:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1507875593.54.0.213398074469.issue31772@psf.upfronthosting.co.za>
In-reply-to
Content
Thanks for the support Nick. I think your proposed idea would still result in rare but confusing behavior, which is the type of surprise Python should avoid.

The hash-based pyc files doesn't seem like a solution to me, because it won't be enabled by default. And I think it's obvious the performance loss of doing so is unacceptable.

If changing the bytecode format is unacceptable, though it seems like the cleanest answer, the import machinery could just avoid caching bytecode when the int(mtime) of the source file is potentially in the future.
History
Date User Action Args
2017-10-13 06:19:53akvadrakosetrecipients: + akvadrako, brett.cannon, ncoghlan, eric.snow
2017-10-13 06:19:53akvadrakosetmessageid: <1507875593.54.0.213398074469.issue31772@psf.upfronthosting.co.za>
2017-10-13 06:19:53akvadrakolinkissue31772 messages
2017-10-13 06:19:53akvadrakocreate