Uh oh!
There was an error while loading. Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork 33.9k
Bring Python into the new year.#24036
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
Uh oh!
There was an error while loading. Please reload this page.
Conversation
ghost commented Jan 1, 2021
There is a "2016" in |
vstinner commented Jan 1, 2021
Last year, @benjaminp did the commit: commit 946b29e. |
vstinner left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
You modified the same files than last year commit, but you also updated PC/python_ver_rc.h which is a good thing.
miss-islington commented Jan 1, 2021
Thanks @corona10 for the PR 🌮🎉.. I'm working now to backport this PR to: 3.6, 3.7, 3.8, 3.9. |
bedevere-bot commented Jan 1, 2021
GH-24045 is a backport of this pull request to the 3.9 branch. |
(cherry picked from commit de6f20a) Co-authored-by: Dong-hee Na <[email protected]>
(cherry picked from commit de6f20a) Co-authored-by: Dong-hee Na <[email protected]>
bedevere-bot commented Jan 1, 2021
GH-24046 is a backport of this pull request to the 3.8 branch. |
bedevere-bot commented Jan 1, 2021
GH-24047 is a backport of this pull request to the 3.7 branch. |
miss-islington commented Jan 1, 2021
Sorry, @corona10, I could not cleanly backport this to |
(cherry picked from commit de6f20a) Co-authored-by: Dong-hee Na <[email protected]>
vstinner commented Jan 1, 2021
This change should not be backported to 3.6 and 3.7, it's not a security fix: https://devguide.python.org/#status-of-python-branches |
(cherry picked from commit de6f20a) Co-authored-by: Dong-hee Na <[email protected]>
(cherry picked from commit de6f20a) Co-authored-by: Dong-hee Na <[email protected]>
ned-deily commented Jan 1, 2021
@vstinner The copyrights are an exception. They should be updated on still active branches. |
miss-islington commented Jan 1, 2021
Thanks @corona10 for the PR 🌮🎉.. I'm working now to backport this PR to: 3.7. |
miss-islington commented Jan 1, 2021
Thanks @corona10 for the PR 🌮🎉.. I'm working now to backport this PR to: 3.6. |
bedevere-bot commented Jan 1, 2021
GH-24052 is a backport of this pull request to the 3.7 branch. |
miss-islington commented Jan 1, 2021
Sorry, @corona10, I could not cleanly backport this to |
(cherry picked from commit de6f20a) Co-authored-by: Dong-hee Na <[email protected]>
ned-deily commented Jan 1, 2021
@corona10 If you would care to deal with the merge conflict for 3.6, I'll see that the PR gets merged. Thanks! |
vstinner commented Jan 1, 2021
Oh. I didn't know, good to know. |
(cherry picked from commit de6f20a) Co-authored-by: Dong-hee Na <[email protected]>
(cherry picked from commit de6f20a) Co-authored-by: Dong-hee Na <[email protected]>
bedevere-bot commented Jan 2, 2021
GH-24054 is a backport of this pull request to the 3.6 branch. |
(cherry picked from commit de6f20a) Co-authored-by: Dong-hee Na <[email protected]>
pombredanne commented Feb 2, 2021 • edited
Loading Uh oh!
There was an error while loading. Please reload this page.
edited
Uh oh!
There was an error while loading. Please reload this page.
Reposting from: Could we stop making these constant changes to the license texts just for a new year? These really do not matter much. Constant changes (as in at least once per year) in the license texts make the downstream identification more complex and brings zero benefits IMHO. |
Happy New Year ;)