>>>>> "GvR" == Guido van Rossum <guido@python.org> writes:
GvR> For regular files I'd leave the formatting alone -- there are
GvR> tools out there that parse these. (E.g. Emacs' Python mode
GvR> jumps to the line with the error if you run a file and it
GvR> begets an exception.)
py-traceback-line-re is what matches those lines. It's current
definition is
(defconst py-traceback-line-re
"[ \t]+File \"\\([^\"]+\\)\", line \\([0-9]+\\)"
"Regular expression that describes tracebacks.")
There are probably also gud.el (and maybe compile.el) regexps that
need to be changed too. I'd rather see something that outputs the
same regardless of whether it's a real file, or something "fake".
Something like
Line 1 of <stdin>
Line 12 of foo.py
should be fine. I'm not crazy about something like
File "foo.py", line 12
In <stdin>, line 1
-Barry
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4