Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork32k
README: Use range of years for copyright#6723
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
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. |
Uses a range of years for Python's copyright rather than listing each year individually.
('2001-2018' vs '2001, 2002, 2003, ...')