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 ezio.melotti
Recipients dmascialino, eric.araujo, ezio.melotti, jjconti, loewis
Date 2011-10-07.20:25:04
SpamBayes Score 6.1871775e-05
Marked as misclassified No
Message-id <1318019105.32.0.409360495996.issue8087@psf.upfronthosting.co.za>
In-reply-to
Content
I'm not sure this is useful to have.  If you changed your code you know that you have to reload, so why would you want a warning that tells you that you changed the code?

For some reason I always had the opposite problem (i.e. after a reload the traceback was still showing the original code, and not the new one), while IIUC you are saying that it shows the new code even if the module is not reloaded.
I tried your code and indeed it does what you say, so either I am mistaken and I've been misreading the tracebacks, or this changed from 2.6 to 2.7, or in some cases even the behavior (I think) I observed might happen.
I'll have to verify this next time it happens.
History
Date User Action Args
2011-10-07 20:25:05ezio.melottisetrecipients: + ezio.melotti, loewis, jjconti, eric.araujo, dmascialino
2011-10-07 20:25:05ezio.melottisetmessageid: <1318019105.32.0.409360495996.issue8087@psf.upfronthosting.co.za>
2011-10-07 20:25:04ezio.melottilinkissue8087 messages
2011-10-07 20:25:04ezio.melotticreate