Bump copyright years to 2019.

[benjaminp]

No description provided.

[eamanu]

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

[benjaminp]

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>.

[eamanu]

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

[pombredanne]

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.