[issue12276] 3.x ignores sys.tracebacklimit=0

2017-11-20 Thread Serhiy Storchaka
Change by Serhiy Storchaka : -- resolution: -> duplicate stage: needs patch -> resolved status: open -> closed superseder: -> Bugs in PyTraceBack_Print() ___ Python tracker __

[issue12276] 3.x ignores sys.tracebacklimit=0

2017-11-05 Thread Serhiy Storchaka
Serhiy Storchaka added the comment: Do you mind to create a pull request on GitHub Anand? Issue31949 fixes this and several other bugs in PyTraceBack_Print(), but it may be worth to fix this bug first, especially if the patch contains tests. -- assignee: docs@python -> serhiy.storchak

[issue12276] 3.x ignores sys.tracebacklimit=0

2017-01-01 Thread Anand Reddy Pandikunta
Anand Reddy Pandikunta added the comment: Update patch with better assertions -- Added file: http://bugs.python.org/file46110/Limit-traceback-if-sys.tracebacklimit-is-set.patch ___ Python tracker _

[issue12276] 3.x ignores sys.tracebacklimit=0

2016-12-27 Thread Anand Reddy Pandikunta
Anand Reddy Pandikunta added the comment: This patch fixes the issue. I have also added 2 test cases to make sure it works. -- keywords: +patch nosy: +ChillarAnand -docs@python Added file: http://bugs.python.org/file46053/Limit-traceback-if-sys.tracebacklimit-is-set.patch

[issue12276] 3.x ignores sys.tracebacklimit=0

2016-08-07 Thread Stéphane Wirtel
Changes by Stéphane Wirtel : -- nosy: +matrixise ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.p

[issue12276] 3.x ignores sys.tracebacklimit=0

2016-08-05 Thread Berker Peksag
Changes by Berker Peksag : -- keywords: +easy stage: -> needs patch type: -> behavior versions: +Python 3.5, Python 3.6 -Python 3.1, Python 3.2 ___ Python tracker ___ _

[issue12276] 3.x ignores sys.tracebacklimit=0

2011-06-10 Thread Terry J. Reedy
Terry J. Reedy added the comment: Either code or doc must change (with 'version changed' note). Doc: "The default is 1000. When set to 0 or less, all traceback information is suppressed and only the exception type and value are printed." Christian's patch: "values <= 0 are replaced with a def

[issue12276] 3.x ignores sys.tracebacklimit=0

2011-06-07 Thread Gabriel Genellina
Gabriel Genellina added the comment: Is this the intended behavior then? I don't get the rationale for that change. There is no way to completely supress traceback information now; for sys.tracebacklimit to be of any significance, it must be >= 1; 0 and negative values behave the same as it n

[issue12276] 3.x ignores sys.tracebacklimit=0

2011-06-07 Thread STINNER Victor
Changes by STINNER Victor : -- nosy: +haypo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue12276] 3.x ignores sys.tracebacklimit=0

2011-06-07 Thread Amaury Forgeot d'Arc
Amaury Forgeot d'Arc added the comment: This was changed a long time ago with 565012d1123d -- nosy: +amaury.forgeotdarc ___ Python tracker ___ __

[issue12276] 3.x ignores sys.tracebacklimit=0

2011-06-07 Thread Gabriel Genellina
Gabriel Genellina added the comment: Originally reported by Thorsten Kampe in comp.lang.python 2011-5-27 -- ___ Python tracker

[issue12276] 3.x ignores sys.tracebacklimit=0

2011-06-07 Thread Gabriel Genellina
New submission from Gabriel Genellina : Python 3.x doesn't honor sys.tracebacklimit=0 According to http://docs.python.org/py3k/library/sys.html#sys.tracebacklimit when set to 0, it should not print any stack trace, but it does. Python 3.2 (r32:88445, Feb 20 2011, 21:29:02) [MSC v.1500 32 bit (