-
-
Notifications
You must be signed in to change notification settings - Fork 30.3k
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
Bring Python into the new year. #24036
Conversation
There is a "2016" in |
f285dc2
to
e6cfd9b
Compare
Last year, @benjaminp did the commit: commit 946b29e. |
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.
Thanks @corona10 for the PR 🌮🎉.. I'm working now to backport this PR to: 3.6, 3.7, 3.8, 3.9. |
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]>
GH-24046 is a backport of this pull request to the 3.8 branch. |
GH-24047 is a backport of this pull request to the 3.7 branch. |
Sorry, @corona10, I could not cleanly backport this to |
(cherry picked from commit de6f20a) Co-authored-by: Dong-hee Na <[email protected]>
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]>
@vstinner The copyrights are an exception. They should be updated on still active branches. |
Thanks @corona10 for the PR 🌮🎉.. I'm working now to backport this PR to: 3.7. |
Thanks @corona10 for the PR 🌮🎉.. I'm working now to backport this PR to: 3.6. |
GH-24052 is a backport of this pull request to the 3.7 branch. |
Sorry, @corona10, I could not cleanly backport this to |
(cherry picked from commit de6f20a) Co-authored-by: Dong-hee Na <[email protected]>
@corona10 If you would care to deal with the merge conflict for 3.6, I'll see that the PR gets merged. Thanks! |
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]>
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]>
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 ;)