GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — README: Use range of years for copyright by Stevoisiak · Pull Request #6723 · python/cpython

Conversation

@Stevoisiak

@Stevoisiak Stevoisiak commented May 7, 2018

Copy link
Copy Markdown
Contributor

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

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

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.
All reactions
@Stevoisiak
README: Use range of years for copyright
9ceeedf 
Uses a range of years for Python's copyright rather than listing each year individually.

('2001-2018' vs '2001, 2002, 2003, ...')
@the-knights-who-say-ni the-knights-who-say-ni added the CLA signed label May 7, 2018
@bedevere-bot bedevere-bot added the awaiting review label May 7, 2018
@serhiy-storchaka

serhiy-storchaka commented May 8, 2018

Copy link
Copy Markdown
Member

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

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.
@ned-deily

ned-deily commented May 8, 2018

Copy link
Copy Markdown
Member

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

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.
@ned-deily ned-deily closed this May 8, 2018
@serhiy-storchaka

serhiy-storchaka commented May 8, 2018

Copy link
Copy Markdown
Member

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

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.
@Stevoisiak
Stevoisiak deleted the patch-2 branch May 9, 2018 15:01
@hugovk hugovk mentioned this pull request Oct 29, 2024
Use static copyright years #126133
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Uh oh!

There was an error while loading. Please reload this page.

Assignees

No one assigned

Labels

awaiting review

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Uh oh!

There was an error while loading. Please reload this page.

5 participants

@Stevoisiak @serhiy-storchaka @ned-deily @the-knights-who-say-ni @bedevere-bot
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.
You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.