README: Use range of years for copyright by Stevoisiak · Pull Request #6723 · 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

Conversation3 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 }})

Uses a range of years for Python's copyright rather than listing each year individually.

('2001-2018' vs '2001, 2002, 2003, ...')

Uses a range of years for Python's copyright rather than listing each year individually.

('2001-2018' vs '2001, 2002, 2003, ...')

Please open an issue on the bug tracker for your change. Since this is related to Python's copyright, it should be approved by BDFL.

I'm sure there are other pull requests and issues that propose this change.

Thanks for your suggestion but, for various reasons, including ease of maintenance across branches, we would prefer to leave the copyright years as they are.

This is a third PR proposing this change. See also #4 and #56.