Skip to content
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

Merged
merged 2 commits into from Jan 1, 2021
Merged

Bring Python into the new year. #24036

merged 2 commits into from Jan 1, 2021

Conversation

@corona10
Copy link
Member

@corona10 corona10 commented Jan 1, 2021

Happy New Year ;)

@animalize
Copy link
Contributor

@animalize animalize commented Jan 1, 2021

There is a "2016" in cpython/PC/python_ver_rc.h, it could be changed to 2021.

@corona10 corona10 requested a review from python/windows-team as a code owner Jan 1, 2021
@corona10 corona10 force-pushed the corona10:happy_new_year branch from f285dc2 to e6cfd9b Jan 1, 2021
@vstinner
Copy link
Member

@vstinner vstinner commented Jan 1, 2021

Last year, @benjaminp did the commit: commit 946b29e.

Copy link
Member

@vstinner vstinner left a comment

LGTM.

You modified the same files than last year commit, but you also updated PC/python_ver_rc.h which is a good thing.

@corona10 corona10 merged commit de6f20a into python:master Jan 1, 2021
11 checks passed
11 checks passed
@github-actions
Docs
Details
@github-actions
Check for source changes
Details
@github-actions
Check if generated files are up to date
Details
@github-actions
Windows (x86)
Details
@github-actions
Windows (x64)
Details
@github-actions
macOS
Details
@github-actions
Ubuntu
Details
Azure Pipelines PR #20210101.17 succeeded
Details
@travis-ci
Travis CI - Pull Request Build Passed
Details
@bedevere-bot
bedevere/issue-number Issue report skipped
@bedevere-bot
bedevere/news "skip news" label found
@miss-islington
Copy link
Contributor

@miss-islington 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
Copy link

@bedevere-bot bedevere-bot commented Jan 1, 2021

GH-24045 is a backport of this pull request to the 3.9 branch.

miss-islington added a commit to miss-islington/cpython that referenced this pull request Jan 1, 2021
(cherry picked from commit de6f20a)

Co-authored-by: Dong-hee Na <donghee.na@python.org>
miss-islington added a commit to miss-islington/cpython that referenced this pull request Jan 1, 2021
(cherry picked from commit de6f20a)

Co-authored-by: Dong-hee Na <donghee.na@python.org>
@bedevere-bot
Copy link

@bedevere-bot bedevere-bot commented Jan 1, 2021

GH-24046 is a backport of this pull request to the 3.8 branch.

@bedevere-bot
Copy link

@bedevere-bot bedevere-bot commented Jan 1, 2021

GH-24047 is a backport of this pull request to the 3.7 branch.

@miss-islington
Copy link
Contributor

@miss-islington miss-islington commented Jan 1, 2021

Sorry, @corona10, I could not cleanly backport this to 3.6 due to a conflict.
Please backport using cherry_picker on command line.
cherry_picker de6f20a6de48d63066b2cf5b317f50629f01d74a 3.6

miss-islington added a commit to miss-islington/cpython that referenced this pull request Jan 1, 2021
(cherry picked from commit de6f20a)

Co-authored-by: Dong-hee Na <donghee.na@python.org>
@vstinner
Copy link
Member

@vstinner 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

miss-islington added a commit that referenced this pull request Jan 1, 2021
(cherry picked from commit de6f20a)

Co-authored-by: Dong-hee Na <donghee.na@python.org>
miss-islington added a commit that referenced this pull request Jan 1, 2021
(cherry picked from commit de6f20a)

Co-authored-by: Dong-hee Na <donghee.na@python.org>
@ned-deily
Copy link
Member

@ned-deily ned-deily commented Jan 1, 2021

@vstinner The copyrights are an exception. They should be updated on still active branches.

@miss-islington
Copy link
Contributor

@miss-islington miss-islington commented Jan 1, 2021

Thanks @corona10 for the PR 🌮🎉.. I'm working now to backport this PR to: 3.7.
🐍🍒🤖

@miss-islington
Copy link
Contributor

@miss-islington miss-islington commented Jan 1, 2021

Thanks @corona10 for the PR 🌮🎉.. I'm working now to backport this PR to: 3.6.
🐍🍒🤖

@bedevere-bot
Copy link

@bedevere-bot bedevere-bot commented Jan 1, 2021

GH-24052 is a backport of this pull request to the 3.7 branch.

@miss-islington
Copy link
Contributor

@miss-islington miss-islington commented Jan 1, 2021

Sorry, @corona10, I could not cleanly backport this to 3.6 due to a conflict.
Please backport using cherry_picker on command line.
cherry_picker de6f20a6de48d63066b2cf5b317f50629f01d74a 3.6

miss-islington added a commit to miss-islington/cpython that referenced this pull request Jan 1, 2021
(cherry picked from commit de6f20a)

Co-authored-by: Dong-hee Na <donghee.na@python.org>
@ned-deily
Copy link
Member

@ned-deily 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
Copy link
Member

@vstinner vstinner commented Jan 1, 2021

@vstinner The copyrights are an exception. They should be updated on still active branches.

Oh. I didn't know, good to know.

ned-deily pushed a commit that referenced this pull request Jan 1, 2021
(cherry picked from commit de6f20a)

Co-authored-by: Dong-hee Na <donghee.na@python.org>
corona10 added a commit to corona10/cpython that referenced this pull request Jan 2, 2021
(cherry picked from commit de6f20a)

Co-authored-by: Dong-hee Na <donghee.na@python.org>
@bedevere-bot
Copy link

@bedevere-bot bedevere-bot commented Jan 2, 2021

GH-24054 is a backport of this pull request to the 3.6 branch.

ned-deily pushed a commit that referenced this pull request Jan 2, 2021
(cherry picked from commit de6f20a)

Co-authored-by: Dong-hee Na <donghee.na@python.org>
@corona10 corona10 deleted the corona10:happy_new_year branch Jan 2, 2021
@pombredanne
Copy link
Contributor

@pombredanne pombredanne commented Feb 2, 2021

Reposting from:
de6f20a#diff-c693279643b8cd5d248172d9c22cb7cf4ed163a3c98c8a3f69c2717edd3eacb7R87

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.

adorilson added a commit to adorilson/cpython that referenced this pull request Mar 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
8 participants