Nick Coghlan <ncogh...@gmail.com> added the comment:

Aye, I think that check would make the most sense, since the bytecode 
invalidation check is "_r_long(raw_timestamp) != source_mtime" (to allow for 
things like version control operations that send source timestamps backwards).

A test for that could then just mock time.time() to make sure it returned  a 
time matching the source mtime, and checked that the bytecode wasn't written.

----------

_______________________________________
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue31772>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Reply via email to