Thanks to visit codestin.com
Credit goes to github.com

Skip to content

change 2.7 status to end-of-life, remove in a few months? #1577

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 and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 20, 2020

Conversation

ned-deily
Copy link
Member

Oops, in #1569, we all overlooked that 2.7 is now end-of-life! While this table is supposed to be active releases, suggest that we leave 2.7 in it for now since this is a major change and consider removing it from here sometime in the future, perhaps after 3.5 is end-of-lifed later this year.

@Mariatta
Copy link
Member

Duplicate of #1577 ?

@ned-deily
Copy link
Member Author

Duplicate of #1577 ?

This is #1577.

@Mariatta
Copy link
Member

Sorry I meant #1576 😥

Copy link
Member

@Mariatta Mariatta left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

end-of-life is more descriptive than EOL so I think this is good.
Thanks.

@ned-deily
Copy link
Member Author

Ah, sorry, I didn't notice #1576 when I opened this one. And, yes, I prefer "end-of-life" as this is an "official" status value in the devguide.

@ned-deily ned-deily merged commit d3247b9 into python:master Apr 20, 2020
@ned-deily
Copy link
Member Author

@ewdurbin, Please deploy when you get a chance. Sorry we missed this on review!

@ned-deily ned-deily deleted the 27-end-of-life branch April 20, 2020 22:30
@ewdurbin
Copy link
Member

done, caches will take a little while to clear and it'll show up :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants