On 12/9/2011 5:17 AM, Nick Coghlan wrote:
As Chris pointed out though, the real problem with the "repeatedly run
2to3" workflow is that it can make interpreting tracebacks from the
field *really* hard.
This just gave me the idea of tagging tracebacks with the Python version
number. Something like
Traceback (Py3.2.2, most recent call last):
and perhaps with the platform also
Traceback (most recent call last) [Py3.2.2 on win23]:
Since computation has stopped, the few extra milliseconds is trivial.
This would certainly help on Python list and the tracker when people do
post the traceback (which they do not always) without version and system
(which they often do not, especially on Python list). It might suggest
to people that this is important info to include. I wonder if this would
also help with tracebacks sent to library/app developers.
--
Terry Jan Reedy
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
