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

Appearance settings

[3.7] bpo-11874: fix assertion failure in argparse metavar handling (GH-1826)#7527

Closed
miss-islington wants to merge 1 commit into
python:3.7python/cpython:3.7from
miss-islington:backport-66f02aa-3.7miss-islington/cpython:backport-66f02aa-3.7Copy head branch name to clipboard
Closed

[3.7] bpo-11874: fix assertion failure in argparse metavar handling (GH-1826)#7527
miss-islington wants to merge 1 commit into
python:3.7python/cpython:3.7from
miss-islington:backport-66f02aa-3.7miss-islington/cpython:backport-66f02aa-3.7Copy head branch name to clipboard

Conversation

@miss-islington

@miss-islington miss-islington commented Jun 8, 2018

Copy link
Copy Markdown
Contributor
  • bugfix and test for fragile metavar handling in argparse (see
    bpo-24089, bpo-14046, bpo-25058, bpo-11874)
  • also fixes some incorrect tests that did not make 1-element tuples correctly
    (cherry picked from commit 66f02aa)

Co-authored-by: wim glenn wim.glenn@gmail.com

https://bugs.python.org/issue11874

…GH-1826)

- bugfix and test for fragile metavar handling in argparse (see
  bpo-24089, bpo-14046, bpo-25058, bpo-11874)
- also fixes some incorrect tests that did not make 1-element tuples correctly
(cherry picked from commit 66f02aa)

Co-authored-by: wim glenn <wim.glenn@gmail.com>
@miss-islington

Copy link
Copy Markdown
Contributor Author

@wimglenn and @ncoghlan: Backport status check is done, and it's a failure ❌ .

1 similar comment
@miss-islington

Copy link
Copy Markdown
Contributor Author

@wimglenn and @ncoghlan: Backport status check is done, and it's a failure ❌ .

@ncoghlan ncoghlan closed this Jun 8, 2018
@miss-islington miss-islington deleted the backport-66f02aa-3.7 branch June 8, 2018 11:06
@ncoghlan

ncoghlan commented Jun 8, 2018

Copy link
Copy Markdown
Contributor

@Mariatta I'm not entirely clear what happened here... I think my closing the PR in order to restart the CI by reopening it may have confused miss-islington.

@ncoghlan

ncoghlan commented Jun 8, 2018

Copy link
Copy Markdown
Contributor

#7530 worked the way we'd expect it to work

@Mariatta

Mariatta commented Jun 8, 2018

Copy link
Copy Markdown
Member

@ncoghlan Yeah that's the tricky part. miss-islington will delete the branch after the PR has been closed, whether merged or not 😄 So re-creating the PR is the way to go, which you already did.

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants

Morty Proxy This is a proxified and sanitized view of the page, visit original site.