- Python Home
- About
- News
- Documentation
- Downloads
- Community
- Foundation
- Developer's Guide
- Issue Tracker
- Issues
- Summaries
- User
- Administration
- Help
Message401554
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.
| Author | paul.j3 |
|---|---|
| Recipients | bigbird, joshmeranda, mhughes, paul.j3, rhettinger, xtreak |
| Date | 2021-09-10.04:42:35 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1631248955.73.0.30170549308.issue41255@roundup.psfhosted.org> |
| In-reply-to |
| Content | |
|---|---|
In https://stackoverflow.com/questions/69108632/unable-to-catch-exception-error-for-argparse we found that `exit_on_error` does not work when the error occurs in a subparser. Unless someone wants to take time to get this right, I think this feature should be removed. It's too buggy. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2021-09-11 05:39:59 | paul.j3 | unlink | issue41255 messages |
| 2021-09-10 04:42:35 | paul.j3 | set | recipients: + paul.j3, rhettinger, xtreak, mhughes, bigbird, joshmeranda |
| 2021-09-10 04:42:35 | paul.j3 | set | messageid: <1631248955.73.0.30170549308.issue41255@roundup.psfhosted.org> |
| 2021-09-10 04:42:35 | paul.j3 | link | issue41255 messages |
| 2021-09-10 04:42:35 | paul.j3 | create | |

