[Python-Dev] Tag trackbacks with version (was Re: readd u'' literal support in 3.3?)

Terry Reedy tjreedy at udel.edu
Sat Dec 10 23:30:49 CET 2011


On 12/10/2011 12:09 PM, PJ Eby wrote:
> On Fri, Dec 9, 2011 at 11:11 PM, Terry Reedy <tjreedy at udel.edu
> <mailto:tjreedy at udel.edu>> wrote:
>
>     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.
>
>
> Yes, but doctest will need to take this into account, both for its
> native traceback matcher, and for traceback matches using ellipses.
>   Otherwise you introduce more Python version hell for doctest users.

Is doctest really insisting that the whole line
   Traceback (most recent call last):
exactly match, with nothing added? It really should not, as that is not 
part of the language spec. This seems like the tail wagging the dog.

-- 
Terry Jan Reedy



More information about the Python-Dev mailing list