Changes by Martin Morrison m...@ensoft.co.uk:
--
nosy: +isoschiz
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14531
___
___
Python-bugs-list
Changes by Ahsan Nawroj ahsan.naw...@gmail.com:
--
nosy: +ainur0160
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14531
___
___
Python-bugs-list
New submission from Edward Yang ezy...@mit.edu:
When generating a backtrace from an interactive Python session (e.g. the input
is from stdin, Python attempts to actually find a file named stdin, to
somewhat hilarious consequences.
See the strace'd Python session below:
foo
Ned Deily n...@acm.org added the comment:
That does seem like silly behavior. On the other hand, the only ill effect is
likely the time required to execute the series of open calls which, in the
interactive case, would not even be noticed on most systems. Would you be
interested in writing
Edward Yang ezy...@mit.edu added the comment:
stdin is a valid name of a file on Unix systems. So the fix is not so clear.
ezyang@javelin:~$ python
Python 2.7.2+ (default, Oct 4 2011, 20:03:08)
[GCC 4.6.1] on linux2
Type help, copyright, credits or license for more information.
a
Traceback
Changes by Antoine Pitrou pit...@free.fr:
--
nosy: +haypo
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14531
___
___
Python-bugs-list mailing
STINNER Victor victor.stin...@gmail.com added the comment:
The filename is retrieved from: traceback-frame-f_code-co_filename.
co_filename is an arbitrary string. Example:
exec(compile(1+a, /etc/passwd, exec))
Traceback (most recent call last):
File stdin, line 1, in module
File
