Skip to content

[3.8] bpo-39450 Stripped whitespace before parsing the docstring in TestCase.shortDescription (GH-18175) #18322

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 our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed

Conversation

miss-islington
Copy link
Contributor

@miss-islington miss-islington commented Feb 3, 2020

(cherry picked from commit 032de73)

Co-authored-by: Steve Cirelli scirelli+git@gmail.com

https://bugs.python.org/issue39450

…e.shortDescription (pythonGH-18175)

(cherry picked from commit 032de73)

Co-authored-by: Steve Cirelli <scirelli+git@gmail.com>
@miss-islington
Copy link
Contributor Author

@scirelli and @cjw296: Status check is done, and it's a failure ❌ .

1 similar comment
@miss-islington
Copy link
Contributor Author

@scirelli and @cjw296: Status check is done, and it's a failure ❌ .

@cjw296 cjw296 closed this Feb 3, 2020
@cjw296 cjw296 reopened this Feb 3, 2020
@miss-islington
Copy link
Contributor Author

@scirelli and @cjw296: Status check is done, and it's a failure ❌ .

@miss-islington miss-islington deleted the backport-032de73-3.8 branch February 3, 2020 07:58
@miss-islington
Copy link
Contributor Author

@scirelli and @cjw296: Status check is done, and it's a failure ❌ .

4 similar comments
@miss-islington
Copy link
Contributor Author

@scirelli and @cjw296: Status check is done, and it's a failure ❌ .

@miss-islington
Copy link
Contributor Author

@scirelli and @cjw296: Status check is done, and it's a failure ❌ .

@miss-islington
Copy link
Contributor Author

@scirelli and @cjw296: Status check is done, and it's a failure ❌ .

@miss-islington
Copy link
Contributor Author

@scirelli and @cjw296: Status check is done, and it's a failure ❌ .

@cjw296
Copy link
Contributor

cjw296 commented Feb 3, 2020

@Mariatta - was trying to close/re-open this as suggested on a python-dev mail thread to get the spurious azure pipeline failure to re-run, but this appears to have made @miss-islington very unhappy...

@aeros
Copy link
Contributor

aeros commented Feb 3, 2020

@cjw296 For @miss-islington specifically, my solution has been to close the backport PR and then re-add the needs-backport-to-x label to the original PR.

@cjw296
Copy link
Contributor

cjw296 commented Feb 3, 2020

Yeah, that's what I ended up doing here.

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