Skip to content

Conversation

@miss-islington
Copy link
Contributor

@miss-islington miss-islington commented Jun 22, 2020

(cherry picked from commit 36ff513)

Co-authored-by: Serhiy Storchaka storchaka@gmail.com

https://bugs.python.org/issue41068

…pythonGH-21040) (cherry picked from commit 36ff513) Co-authored-by: Serhiy Storchaka <storchaka@gmail.com>
@miss-islington
Copy link
Contributor Author

@serhiy-storchaka: Status check is done, and it's a success ✅ .

@miss-islington
Copy link
Contributor Author

Sorry, I can't merge this PR. Reason: You're not authorized to push to this branch. Visit https://help.github.com/articles/about-protected-branches/ for more information..

@miss-islington
Copy link
Contributor Author

@serhiy-storchaka: Status check is done, and it's a success ✅ .

@miss-islington
Copy link
Contributor Author

Sorry, I can't merge this PR. Reason: You're not authorized to push to this branch. Visit https://help.github.com/articles/about-protected-branches/ for more information..

@ned-deily
Copy link
Member

As announced, with the tagging of 3.7.8rc1, the 3.7 branch is now in security-fix mode. This change doesn't strike me as meeting the criteria for either a security fix or a release-critical fix for 3.7.8 final. I'm reluctant to throw this change in at the last minute but if you can get another core developer to review and approve it, I'll consider it.

@ned-deily
Copy link
Member

3.7.8 is now released and 3.7 is now in security-fix mode

@ned-deily ned-deily closed this Jun 28, 2020
@miss-islington miss-islington deleted the backport-36ff513-3.7 branch June 28, 2020 13:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

awaiting merge type-bug An unexpected behavior, bug, or error

5 participants