[issue14531] Backtrace should not attempt to open file

2020-11-15 Thread Irit Katriel
Change by Irit Katriel : -- resolution: -> duplicate stage: needs patch -> resolved status: open -> closed superseder: -> Traceback display code can attempt to open a file named "" ___ Python tracker _

[issue14531] Backtrace should not attempt to open file

2013-04-20 Thread Martin Morrison
Changes by Martin Morrison : -- nosy: +isoschiz ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyt

[issue14531] Backtrace should not attempt to open file

2012-09-06 Thread Ahsan Nawroj
Changes by Ahsan Nawroj : -- nosy: +ainur0160 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pytho

[issue14531] Backtrace should not attempt to open file

2012-04-08 Thread STINNER Victor
STINNER Victor 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 "", line 1, in File "/etc/passwd", line 1, in

[issue14531] Backtrace should not attempt to open file

2012-04-08 Thread Antoine Pitrou
Changes by Antoine Pitrou : -- nosy: +haypo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue14531] Backtrace should not attempt to open file

2012-04-08 Thread Edward Yang
Edward Yang added the comment: "" 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 (most re

[issue14531] Backtrace should not attempt to open file

2012-04-08 Thread Ned Deily
Ned Deily 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 a patch? ---

[issue14531] Backtrace should not attempt to open file

2012-04-08 Thread Edward Yang
New submission from Edward Yang : When generating a backtrace from an interactive Python session (e.g. the input is from , Python attempts to actually find a file named , to somewhat hilarious consequences. See the strace'd Python session below: >>> foo open("/etc/default/apport", O_RDONLY|O_