bpo-17050: Remove documentation on argparse.REMAINDER#18661
Conversation
|
Hello, and thanks for your contribution! I'm a bot set up to make sure that the project can legally accept this contribution by verifying everyone involved has signed the PSF contributor agreement (CLA). Recognized GitHub usernameWe couldn't find a bugs.python.org (b.p.o) account corresponding to the following GitHub usernames: This might be simply due to a missing "GitHub Name" entry in one's b.p.o account settings. This is necessary for legal reasons before we can look at this contribution. Please follow the steps outlined in the CPython devguide to rectify this issue. You can check yourself to see if the CLA has been received. Thanks again for the contribution, we look forward to reviewing it! |
Sorry, something went wrong.
|
I've already signed the CLA and I'm currently just waiting for it to get accepted. Regarding the bedevere/news CI failure, I'm a bit confused by it because the docs on news blurbs states that "Changes that affect documentation only generally do not require a news entry.". Is there something I'm missing? |
Sorry, something went wrong.
eamanu
left a comment
There was a problem hiding this comment.
LGTM.
Sorry, something went wrong.
|
@corollari yes you are right, this PR does not need a NEWs. |
Sorry, something went wrong.
|
Thanks @corollari for the PR 🌮🎉.. I'm working now to backport this PR to: 3.9. |
Sorry, something went wrong.
Closes Issue 17050 by removing argparse.REMAINDER from the documentation, as discussed on the issue.
https://bugs.python.org/issue17050
Automerge-Triggered-By: @rhettinger