Author scoder
Recipients Steve Pryde, jfine2358, scoder, steven.daprano, xtreak
Date 2019-01-30.17:35:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1548869749.21.0.87865415978.issue35857@roundup.psfhosted.org>
In-reply-to
Content
I think the REPL could, when it formats a stack trace for printing, check every referenced source file if it's newer than its compiled .pyc (bytecode) file, and insert a warning into the stack trace if that is the case.

I don't see any use in doing this for all stack traces, so only ones that get printed out for the user could receive special treatment.

I also don't think we need to go further than that, e.g. check startup or module import time. Basically, whenever the source file is not in sync with the .pyc file, it's not unlikely that the code that is running corresponds to the .pyc file and no longer to the .py file.

Changing to target version to 3.8, since this is essentially a new feature and not acceptable as a bug fix for older versions.
History
Date User Action Args
2019-01-30 17:35:51scodersetrecipients: + scoder, steven.daprano, xtreak, jfine2358, Steve Pryde
2019-01-30 17:35:49scodersetmessageid: <1548869749.21.0.87865415978.issue35857@roundup.psfhosted.org>
2019-01-30 17:35:49scoderlinkissue35857 messages
2019-01-30 17:35:49scodercreate