Bring Python into the new year.#24036
Conversation
|
There is a "2016" in |
Sorry, something went wrong.
f285dc2 to
e6cfd9b
Compare
January 1, 2021 14:24
vstinner
left a comment
There was a problem hiding this 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.
Sorry, something went wrong.
|
Thanks @corona10 for the PR 🌮🎉.. I'm working now to backport this PR to: 3.6, 3.7, 3.8, 3.9. |
Sorry, something went wrong.
(cherry picked from commit de6f20a) Co-authored-by: Dong-hee Na <donghee.na@python.org>
(cherry picked from commit de6f20a) Co-authored-by: Dong-hee Na <donghee.na@python.org>
|
Sorry, @corona10, I could not cleanly backport this to |
Sorry, something went wrong.
(cherry picked from commit de6f20a) Co-authored-by: Dong-hee Na <donghee.na@python.org>
|
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 |
Sorry, something went wrong.
(cherry picked from commit de6f20a) Co-authored-by: Dong-hee Na <donghee.na@python.org>
(cherry picked from commit de6f20a) Co-authored-by: Dong-hee Na <donghee.na@python.org>
|
@vstinner The copyrights are an exception. They should be updated on still active branches. |
Sorry, something went wrong.
|
Thanks @corona10 for the PR 🌮🎉.. I'm working now to backport this PR to: 3.7. |
Sorry, something went wrong.
|
Thanks @corona10 for the PR 🌮🎉.. I'm working now to backport this PR to: 3.6. |
Sorry, something went wrong.
|
Sorry, @corona10, I could not cleanly backport this to |
Sorry, something went wrong.
(cherry picked from commit de6f20a) Co-authored-by: Dong-hee Na <donghee.na@python.org>
|
@corona10 If you would care to deal with the merge conflict for 3.6, I'll see that the PR gets merged. Thanks! |
Sorry, something went wrong.
Oh. I didn't know, good to know. |
Sorry, something went wrong.
(cherry picked from commit de6f20a) Co-authored-by: Dong-hee Na <donghee.na@python.org>
|
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. |
Sorry, something went wrong.
Happy New Year ;)