➜
This issue tracker has been migrated to GitHub,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
Created on 2015-09-06 10:36 by xdegaye, last changed 2022-04-11 14:58 by admin.
| Files | ||||
|---|---|---|---|---|
| File name | Uploaded | Description | Edit | |
| run_pdb.patch | xdegaye, 2015-09-06 10:36 | review | ||
| Messages (2) | |||
|---|---|---|---|
| msg249989 - (view) | Author: Xavier de Gaye (xdegaye) *  |
Date: 2015-09-06 10:36 | |
The attached patch fixes this. |
|||
| msg250065 - (view) | Author: Terry J. Reedy (terry.reedy) *  |
Date: 2015-09-07 05:28 | |
Xavier, thanks for the idea. It seems sensible and I considered applying this, but since this is an internal pdb test design change rather than a pdb bug fix, and two other tests seem candidates for the same change, I am going to leave it to Gerog or someone else to review. I do not understand the details of run_pdb, the reason why some tests use it and other inline a subprocess call, or why they all mix together stdout and stderr. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:58:20 | admin | set | github: 69201 |
| 2015-09-07 05:28:56 | terry.reedy | set | nosy:
+ georg.brandl messages: + msg250065 components: + Tests stage: patch review |
| 2015-09-06 10:36:43 | xdegaye | create | |