Diego Mascialino added the comment:
> 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 app
Diego Mascialino added the comment:
On Fri, Oct 7, 2011 at 5:25 PM, Ezio Melotti wrote:
>
> Ezio Melotti added the comment:
>
> 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 tha
Diego Mascialino added the comment:
I worked a few hours today and I have this patch.
I tried to make a test but could not.
I know this is not a really good patch, but it's my first one and I wanted to
show my idea.
--
keywords: +patch
versions: -Python 2.7
Added file:
Diego Mascialino added the comment:
Martin, I am not talking about a loop checking source file changes.
I think the check could be done only when the traceback is printed.
The function PyErr_Display() calls PyTracBack_Print() and so on until
_Py_DisplaySourceLine() is called. The latter
New submission from Diego Mascialino :
Example:
mod.py
def f():
a,b,c = 1,2
print b
If i do:
>>> import mod
>>> mod.f()
I get:
Traceback (most recent call last):
File "", line 1,
