Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #9415 > unrolled thread

Re: sys.tracebacklimit

Started byChris Rebert <clp2@rebertia.com>
First post2011-07-13 10:10 -0700
Last post2011-07-13 10:10 -0700
Articles 1 — 1 participant

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: sys.tracebacklimit Chris Rebert <clp2@rebertia.com> - 2011-07-13 10:10 -0700

#9415 — Re: sys.tracebacklimit

FromChris Rebert <clp2@rebertia.com>
Date2011-07-13 10:10 -0700
SubjectRe: sys.tracebacklimit
Message-ID<mailman.999.1310577048.1164.python-list@python.org>
On Wed, Jul 13, 2011 at 6:42 AM, Vlad Didenko <vdidenko@getcollc.com> wrote:
> Colleagues,
> Per documentation
> at http://docs.python.org/py3k/library/sys.html#sys.tracebacklimit :
>      When [sys.tracebacklimit] set to 0 or less, all traceback information
> is suppressed and only the exception type and value are printed
> So, I expect to be able to have a program like:
>     import sys
>     sys.tracebacklimit=0
>     print(1/0)
> And see it's result as:
>      ZeroDivisionError: division by zero
> However, the actual result is:
>      Traceback (most recent call last):
>        File "tbt.py", line 3, in <module>
>          print(1/0)
>      ZeroDivisionError: division by zero
> Do I misunderstand the docs?

Nope. It's a known bug:
http://bugs.python.org/issue12276

Cheers,
Chris

[toc] | [standalone]


Back to top | Article view | comp.lang.python


csiph-web