Bump copyright years to 2019. by benjaminp · Pull Request #11404 · python/cpython (original) (raw)

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 andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Conversation4 Commits1 Checks0 Files changed

Conversation

This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters

[ Show hidden characters]({{ revealButtonHref }})

@benjaminp It would be interest have a the way to make the copyright year automagically, isn't?

I mean, for example use SOURCE_DATE_EPOCH to made it reproducible or use time.time().

benjaminp added a commit that referenced this pull request

Jan 2, 2019

(cherry picked from commit 9a69ae8)

Co-authored-by: Benjamin Peterson benjamin@python.org

benjaminp added a commit that referenced this pull request

Jan 2, 2019

(cherry picked from commit 9a69ae8)

Co-authored-by: Benjamin Peterson benjamin@python.org

benjaminp added a commit that referenced this pull request

Jan 2, 2019

(cherry picked from commit 9a69ae8)

Co-authored-by: Benjamin Peterson benjamin@python.org

Could we stop making these updates to years in copyright statements? they are eventually creating a burden on anyone that reuses Python code as the license is updated. It is also kind of silly to me to have the Python license text change each year.

I would make a plea for year-less copyright. The expiration of these copyrights is something that's not driven by a year mentioned in such notice anyway.