➜

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-08.13:03:02
SpamBayes Score 1.7300141e-06
Marked as misclassified No
Message-id <1318078983.36.0.655456319723.issue8087@psf.upfronthosting.co.za>
In-reply-to
Content 
> The source line showed in the traceback could not be the same line executed.

My point is that when I see an error and modify the source to fix it, then I know that I'll have to reload.  If for some reason I forget to reload, I'll get the wrong line in the traceback and then reload, but I don't think that ever happened to me.
So to me, your warning will only be useful in the case where I modified the source, forgot to reload and got the same error again with a wrong line displayed.  Also note that reloading is not so common; usually you just restart your application and that will give you the right traceback.

Also I'm not sure the warning you proposed is the best way to handle this.
History
Date User Action Args
2011-10-08 13:03:03ezio.melottisetrecipients: + ezio.melotti, loewis, jjconti, eric.araujo, dmascialino
2011-10-08 13:03:03ezio.melottisetmessageid: <1318078983.36.0.655456319723.issue8087@psf.upfronthosting.co.za>
2011-10-08 13:03:02ezio.melottilinkissue8087 messages
2011-10-08 13:03:02ezio.melotticreate