Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

bpo-17050: Remove documentation on argparse.REMAINDER#18661

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
miss-islington merged 1 commit intopython:masterfromcorollari:master
May 24, 2020

Conversation

corollari
Copy link
Contributor

@corollaricorollari commentedFeb 25, 2020
edited by miss-islington
Loading

ClosesIssue 17050 by removing argparse.REMAINDER from the documentation, as discussed on the issue.

https://bugs.python.org/issue17050

Automerge-Triggered-By:@rhettinger

pxeger, Jwink3101, fwcd, and rindeal reacted with thumbs down emoji
@the-knights-who-say-ni

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 thePSF contributor agreement (CLA).

Recognized GitHub username

We couldn't find abugs.python.org (b.p.o) account corresponding to the following GitHub usernames:

@corollari

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 followthe steps outlined in the CPython devguide to rectify this issue.

You cancheck yourself to see if the CLA has been received.

Thanks again for the contribution, we look forward to reviewing it!

@corollari
Copy link
ContributorAuthor

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 thedocs on news blurbs states that "Changes that affect documentation only generally do not require a news entry.". Is there something I'm missing?

Copy link
Contributor

@eamanueamanu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

LGTM.

@eamanu
Copy link
Contributor

@corollari yes you are right, this PR does not need a NEWs.

@miss-islington
Copy link
Contributor

@corollari: Status check is done, and it's a success ✅ .

@miss-islingtonmiss-islington merged commit59f5022 intopython:masterMay 24, 2020
@miss-islington
Copy link
Contributor

Thanks@corollari for the PR 🌮🎉.. I'm working now to backport this PR to: 3.9.
🐍🍒⛏🤖

@bedevere-bot
Copy link

GH-20363 is a backport of this pull request to the3.9 branch.

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers

@rhettingerrhettingerrhettinger approved these changes

@eamanueamanueamanu approved these changes

Assignees
No one assigned
Labels
docsDocumentation in the Doc dirskip news
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

6 participants
@corollari@the-knights-who-say-ni@eamanu@miss-islington@bedevere-bot@rhettinger

[8]ページ先頭

©2009-2025 Movatter.jp