README: Use range of years for copyright #6723
Closed
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
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. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uses a range of years for Python's copyright rather than listing each year individually.
('2001-2018' vs '2001, 2002, 2003, ...')