The Wayback Machine - https://web.archive.org/web/20211124030737/https://github.com/python/cpython/pull/11404
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

Bump copyright years to 2019. #11404

Merged
merged 1 commit into from Jan 2, 2019
Merged

Bump copyright years to 2019. #11404

merged 1 commit into from Jan 2, 2019

Conversation

@benjaminp
Copy link
Contributor

@benjaminp benjaminp commented Jan 2, 2019

No description provided.

@eamanu
Copy link
Contributor

@eamanu eamanu commented Jan 2, 2019

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

Loading

@benjaminp
Copy link
Contributor Author

@benjaminp benjaminp commented Jan 2, 2019

Loading

@eamanu
Copy link
Contributor

@eamanu eamanu commented Jan 2, 2019

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

Loading

eamanu
eamanu approved these changes Jan 2, 2019
@benjaminp benjaminp merged commit 9a69ae8 into python:master Jan 2, 2019
5 checks passed
Loading
@benjaminp benjaminp deleted the 2019-copyright branch Jan 2, 2019
benjaminp added a commit that referenced this issue Jan 2, 2019
(cherry picked from commit 9a69ae8)

Co-authored-by: Benjamin Peterson <[email protected]>
benjaminp added a commit that referenced this issue Jan 2, 2019
(cherry picked from commit 9a69ae8)

Co-authored-by: Benjamin Peterson <[email protected]>
benjaminp added a commit that referenced this issue Jan 2, 2019
(cherry picked from commit 9a69ae8)

Co-authored-by: Benjamin Peterson <[email protected]>
arnolddumas added a commit to arnolddumas/cpython that referenced this issue May 3, 2019
@pombredanne
Copy link
Contributor

@pombredanne pombredanne commented May 24, 2019

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.

Loading

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
5 participants