Irit Katriel added the comment:
The patch here added a reference from TracebackException to the actual
traceback, which I think should be removed. Please see this issue:
https://bugs.python.org/issue42482
--
nosy: +iritkatriel
___
Python tracker
Berker Peksag added the comment:
Looks like a cache issue. I've just fixed it:
https://docs.python.org/3.5/whatsnew/changelog.html
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24695
___
Adam Bartoš added the comment:
I meant this one:
https://docs.python.org/3.5/whatsnew/changelog.html#python-3-5-beta-4 .
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24695
___
Adam Bartoš added the comment:
Ok, thanks.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24695
___
___
Python-bugs-list mailing list
Adam Bartoš added the comment:
Just out of my curiosity – why is not this issue listed in Python 3.5b4
changelog even though the issue is fixed there?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24695
Berker Peksag added the comment:
Could you please share the link of the changelog you've mentioned? Unless I'm
missing something, this issue is already listed in the changelog:
https://hg.python.org/releasing/3.5/file/f65605b99cb4/Misc/NEWS#l37
--
Roundup Robot added the comment:
New changeset b45077269aaa by Berker Peksag in branch '3.5':
Issue #24695: Fix a regression in traceback.print_exception()
https://hg.python.org/cpython/rev/b45077269aaa
New changeset 2825c87d3f72 by Berker Peksag in branch 'default':
Issue #24695: Fix a
Berker Peksag added the comment:
Fixed in 3.5 and default branches. Thank you for your review, Raymond.
--
resolution: - fixed
stage: patch review - resolved
status: open - closed
___
Python tracker rep...@bugs.python.org
Adam Bartoš added the comment:
Thank you all for a quick reaction.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24695
___
___
Python-bugs-list
Berker Peksag added the comment:
Here is a patch. I was pretty sure that I've already created an issue for this
but couldn't find it now.
--
keywords: +patch
nosy: +berker.peksag
stage: needs patch - patch review
Added file: http://bugs.python.org/file40001/issue24695.diff
Raymond Hettinger added the comment:
This patch looks correct, applies cleanly, and passes tests.
--
nosy: +rhettinger
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24695
___
New submission from Adam Bartoš:
The documentation of traceback.print_exception says if traceback is not None,
it prints a header Traceback (most recent call last):. That also meant that
the header wasn't printed if traceback was None. However, the new Python 3.5
TracebackException object
Changes by R. David Murray rdmur...@bitdance.com:
--
stage: - needs patch
title: Don't print traceback header if traceback is None - Don't print
traceback header if traceback is None in TracebackException
versions: +Python 3.6
___
Python tracker
Changes by Berker Peksag berker.pek...@gmail.com:
--
nosy: +rbcollins
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24695
___
___
Python-bugs-list
Robert Collins added the comment:
Huh,indeed.
So clearly we should have a test for that behaviour (and fix it).
We're very close to the 3.5 release date, but this is a regression - care to
whip up a patch?
--
___
Python tracker
15 matches
Mail list logo
