Perfect your code
With built-in code review tools, GitHub makes it easy to raise the quality bar before you ship. Join the 40 million developers who've merged over 200 million pull requests.
Sign up for free See pricing for teams and enterprisesBump copyright years to 2019. #11404
Conversation
This comment has been minimized.
This comment has been minimized.
|
@benjaminp It would be interest have a the way to make the copyright year automagically, isn't? |
This comment has been minimized.
This comment has been minimized.
|
I made this with search-and-replace. How much more "automagic" does it need to be?
…On Wed, Jan 2, 2019, at 06:24, Emmanuel Arias wrote:
@benjaminp <https://github.com/benjaminp> It would be interest have a
the way to make the copyright year automagically, isn't?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#11404 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AANZTm2dR_at4x9baOwJBGaCJ2QL8NNOks5u_MEpgaJpZM4Zmtr9>.
|
This comment has been minimized.
This comment has been minimized.
|
I mean, for example use SOURCE_DATE_EPOCH to made it reproducible or use time.time(). |
This comment has been minimized.
This comment has been minimized.
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. |
benjaminp commentedJan 2, 2019
No description provided.