Message340117
| Author | Saim Raza |
|---|---|
| Recipients | Saim Raza, SilentGhost, barry, xdegaye |
| Date | 2019-04-12.22:24:17 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1555107857.17.0.151783097248.issue36537@roundup.psfhosted.org> |
| In-reply-to |
| Content | |
|---|---|
> Knowing that pdb stops just before the interpreter executes the line after pdb.set_trace(), what prevents you from writing the pdb.set_trace() statement before the last line of the except clause ? Of course, that can be done. The issue here is to get the correct and expected behavior from pdb/ipdb. On a similar note, users might want to put just the set_trace() call and no other code in the block while writing the code or during debugging the exception caught. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2019-04-12 22:24:17 | Saim Raza | set | recipients: + Saim Raza, barry, SilentGhost, xdegaye |
| 2019-04-12 22:24:17 | Saim Raza | set | messageid: <1555107857.17.0.151783097248.issue36537@roundup.psfhosted.org> |
| 2019-04-12 22:24:17 | Saim Raza | link | issue36537 messages |
| 2019-04-12 22:24:17 | Saim Raza | create | |