Message304373
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. |
|
Date |
User |
Action |
Args |
2017-10-14 04:33:41 | ncoghlan | set | recipients:
+ ncoghlan, brett.cannon, eric.snow, akvadrako |
2017-10-14 04:33:41 | ncoghlan | set | messageid: <1507955621.54.0.213398074469.issue31772@psf.upfronthosting.co.za> |
2017-10-14 04:33:41 | ncoghlan | link | issue31772 messages |
2017-10-14 04:33:40 | ncoghlan | create | |
|