Author dmascialino
Recipients dmascialino, eric.araujo, ezio.melotti, jjconti, loewis
Date 2011-10-08.15:52:42
SpamBayes Score 1.2079e-09
Marked as misclassified No
Message-id <CAN+O6V0bwhCaY575E-wR5hd148t1uocG=ynG4O8y8o970Kj9Bw@mail.gmail.com>
In-reply-to <1318078983.36.0.655456319723.issue8087@psf.upfronthosting.co.za>
Content
> 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.

I know the case when this happens is really unsusual, but the
interperter could be able to alert you than that line of the traceback
is wrong.

> Also I'm not sure the warning you proposed is the best way to handle this.

I agree that, another approach is to save a copy of the source file
associated to the compiled code (like a .pys).
History
Date User Action Args
2011-10-08 15:52:43dmascialinosetrecipients: + dmascialino, loewis, jjconti, ezio.melotti, eric.araujo
2011-10-08 15:52:42dmascialinolinkissue8087 messages
2011-10-08 15:52:42dmascialinocreate