Mark myagn...@students.poly.edu added the comment:
Yay! I can't wait :)
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15262
___
___
Terry J. Reedy tjre...@udel.edu added the comment:
Unless this could have been just as easily fixed in IDLE as in the core
(Roger?), no, don't hold your breath ;-).
--
nosy: +serwy
___
Python tracker rep...@bugs.python.org
Roger Serwy roger.se...@gmail.com added the comment:
Mark, I ran your example against 2.7.1 and did not receive a traceback. I then
ran it against the latest 2.7.3+ and receive a traceback in IDLE. Here's the
entire Shell contents:
Python 2.7.3+ (2.7:97445ca895d5, Jul 8 2012, 19:58:43)
Terry J. Reedy tjre...@udel.edu added the comment:
Thanks Roger. So this should be fixed in the upcoming 2.7.4 and probably 3.2.4.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15262
___
New submission from Mark myagn...@students.poly.edu:
Consider the following code:
from thread import start_new
def f(): typo #there is no variable called typo
start_new(f, ())
If run from the command line, this produces a traceback. If run from IDLE, it
does not. I suspect this is not by
Terry J. Reedy tjre...@udel.edu added the comment:
In 3.3, you do not need it
Unhandled exception in thread started by function f at 0x031D0158
Traceback (most recent call last):
File F:\Python\mypy\tem.py, line 2, in f
def f(): typo #there is no variable called typo
NameError:
Mark myagn...@students.poly.edu added the comment:
So, I should not hold my breath in the hope of this being fixed in 2.7?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15262
___
