[issue34945] regression with ./python -m test and pdb

Pablo Galindo Salgado added the comment: 3.6 and 3.7 are backported! -- stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue34945] regression with ./python -m test and pdb

miss-islington added the comment: New changeset 7b689c68ab3236455f7d58954435d029e2bb2c8a by Miss Islington (bot) in branch '3.6': bpo-34945: Buffer output in test suite only when creating junit file (GH-10204) https://github.com/python/cpython/commit/7b689c68ab3236455f7d58954435d029e2bb2c8a

[issue34945] regression with ./python -m test and pdb

miss-islington added the comment: New changeset 58f7bf3a892031616a6b06ef4b8d36e2ebec172b by Miss Islington (bot) in branch '3.7': bpo-34945: Buffer output in test suite only when creating junit file (GH-10204) https://github.com/python/cpython/commit/58f7bf3a892031616a6b06ef4b8d36e2ebec172b

[issue34945] regression with ./python -m test and pdb

Change by miss-islington : -- pull_requests: +9542 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34945] regression with ./python -m test and pdb

Change by miss-islington : -- pull_requests: +9541 stage: resolved -> patch review ___ Python tracker ___ ___ Python-bugs-list

[issue34945] regression with ./python -m test and pdb

STINNER Victor added the comment: At least Python 3.6 and 3.7 branches are affected as well, so I reopen the issue. -- status: closed -> open versions: +Python 3.6, Python 3.7 ___ Python tracker

[issue34945] regression with ./python -m test and pdb

Pablo Galindo Salgado added the comment: This should be fixed (it works now with and without -v). :) -- stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue34945] regression with ./python -m test and pdb

Pablo Galindo Salgado added the comment: New changeset 02277482ea765335e497ecd9661d4bde9b5ddc67 by Pablo Galindo in branch 'master': bpo-34945: Buffer output in test suite only when creating junit file (GH-10204)

[issue34945] regression with ./python -m test and pdb

Stéphane Wirtel added the comment: Pablo, I have tested your PR and I get the prompt of pdb only if I use -v on the command line. For the print() function, I understand but for the pdb.set_trace() function, normally we should have the prompt even we don't specify the --verbose flat. Do you

[issue34945] regression with ./python -m test and pdb

Change by Pablo Galindo Salgado : -- keywords: +patch pull_requests: +9522 stage: -> patch review ___ Python tracker ___ ___

[issue34945] regression with ./python -m test and pdb

Steve Dower added the comment: Thanks for spotting this! There's no "rationale" for hiding the output - what happened is I streamlined the test suite to always capture output, instead of some tests deciding whether they ought to capture it or not (and some doing incredibly weird things when

[issue34945] regression with ./python -m test and pdb

STINNER Victor added the comment: More generally, previously it was possible to add print("HERE") in tests. I use that often do debug tests. Now, the output is hidden, I don't understand the rationale for hiding the output. -- nosy: +vstinner ___

[issue34945] regression with ./python -m test and pdb

Change by Stéphane Wirtel : -- title: regression with ./python -m test -> regression with ./python -m test and pdb ___ Python tracker ___