Message339583
| Author | blueyed |
|---|---|
| Recipients | blueyed |
| Date | 2019-04-07.19:15:47 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1554664547.38.0.626848411176.issue36550@roundup.psfhosted.org> |
| In-reply-to |
| Content | |
|---|---|
pdb should try (hard) to avoid creating unnecessary exceptions, e.g. ``AttributeError`` when looking up commands, since this will show up in exception chains then (as "'Pdb' object has no attribute 'do_foo'"). See https://github.com/python/cpython/pull/4666 for an older PR in this regard. My use case is to display the traceback for exceptions caused within/via Pdb.default(), to see more context when running code from pdb's prompt directly, where currently it would only display the exception itself. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2019-04-07 19:15:47 | blueyed | set | recipients: + blueyed |
| 2019-04-07 19:15:47 | blueyed | set | messageid: <1554664547.38.0.626848411176.issue36550@roundup.psfhosted.org> |
| 2019-04-07 19:15:47 | blueyed | link | issue36550 messages |
| 2019-04-07 19:15:47 | blueyed | create | |