| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
@nejch Seems like Python 3.11.0-beta.1 doesn't like what we are doing... |
Sorry, something went wrong.
|
I think this is the upstream commit: commit ad5e8520f3e117f45481513014548a39879d30d2
Author: Antony Lee <anntzer.lee@gmail.com>
Date: Sun May 1 08:04:50 2022 +0200
bpo-39716: Raise on conflicting subparser names. (GH-18605)
Raise an ArgumentError when the same subparser name is added twice to an
ArgumentParser. This is consistent with the (default) behavior when the
same option string is added twice to an ArgumentParser.
(Support for `conflict_handler="resolve"` could be considered as a
followup feature, although real use cases seem even rarer than
"resolve"ing option-strings.)
Automerge-Triggered-By: GH:rhettinger
|
Sorry, something went wrong.
|
The PR upstream: python/cpython#18605 |
Sorry, something went wrong.
|
Probably should create an issue for this instead of my dummy PR 😊 |
Sorry, something went wrong.
Codecov Report
@@ Coverage Diff @@
## main #2014 +/- ##
==========================================
- Coverage 92.65% 92.62% -0.04%
==========================================
Files 78 78
Lines 4944 4949 +5
==========================================
+ Hits 4581 4584 +3
- Misses 363 365 +2
Flags with carried forward coverage won't be shown. Click here to find out more.
|
Sorry, something went wrong.
Python 3.11 added an additional check in the argparse libary which detected duplicate subparsers being added. We had duplicate subparsers being added. Make sure we don't add duplicate subparsers. Closes: #2015
| Back | FazBrowse Home | New Git URL |
Python 3.11 added an additional check in the argparse libary which
detected duplicate subparsers being added. We had duplicate subparsers
being added.
Make sure we don't add duplicate subparsers.
Closes: #2015