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

Skip to content

Add archive section #293

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.

Sign up for GitHub

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 2 commits into from
Apr 18, 2024
Merged

Add archive section #293

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
83e6131
Add archive section
takluyver Apr 12, 2024
b2dca6a
Add archival note to README as well
takluyver Apr 18, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
39 changes: 35 additions & 4 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,36 @@
This is the main website for a pledge to stop supporting Python 2 for free in
open source software.

# Run locally
## History

This page is now an archive of part of the transition from Python 2 to 3.

By around 2015, when Python 2 support was originally planned to end, many
important Python libraries and tools supported Python 3. But Python 2 still had
a lot of users, and projects needed to support both major versions. The end of
Python 2 support was postponed to 2020, and some people argued that development
of Python 2 should resume. It seemed like a real possibility that the end date
would be postponed again, and we'd need to support two versions of the language
indefinitely.

The Python 3 statement was drawn up around 2016. Projects pledged to require
Python 3 by 2020, giving other projects confidence that they could plan a similar
transition, and allowing downstream users to figure out their options without a
nasty surprise. We didn't force people to move to Python 3, but if they wanted
to stick with Python 2, they would stop getting new versions of our projects.
The focus was originally on the scientific Python ecosystem, with Jupyter and
matplotlib among the first projects involved, but in late 2017 it was expanded
to any Python projects.
A rapidly growing number of projects signed up as we approached 2020.

The long-term transition we hoped for has succeeded: in 2024 it is entirely
normal for projects to support only Python 3, simplifying maintainers' lives
and letting us take full advantage of newer language features.

Thank-you to all of the people, in projects big and small, who contributed
their support to the statement!

## Run locally

Install Jekyll : `gem install jekyll`, `gem install github-pages`

Expand All @@ -15,7 +44,9 @@ Modify the various files, refresh your browser and enjoy.

PRs welcomed.

# Add your project
## Add your project

We're no longer adding new projects - see the history section above.

If you just want to add your project to the list of participating projects, add
a line in [the list of participating projects](_sections/30-projects.md). It's
Expand All @@ -25,7 +56,7 @@ online](https://github.com/python3statement/python3statement.github.io/edit/mast

There is no need to install Jekyll: A check creating a preview will be run on your pull request. Please check this preview.

## Add timeline information
### Add timeline information

The front page also has a timeline chart, with past release dates and future
(planned) releases. You can also add your project there, if you have a specific
Expand All @@ -35,7 +66,7 @@ See [site.js](site.js) around [line
100](https://github.com/python3statement/python3statement.github.io/blob/master/site.js#L103)
to see how to add this kind of data.

# Base template
## Base template

This site is based on
[github.com/t413/SinglePaged](https://github.com/t413/SinglePaged).
33 changes: 33 additions & 0 deletions _sections/10-archive.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,33 @@
---
title: archive
bg: 'white'
---

# History

This page is now an archive of part of the transition from Python 2 to 3.

By around 2015, when Python 2 support was originally planned to end, many
important Python libraries and tools supported Python 3. But Python 2 still had
a lot of users, and projects needed to support both major versions. The end of
Python 2 support was postponed to 2020, and some people argued that development
of Python 2 should resume. It seemed like a real possibility that the end date
would be postponed again, and we'd need to support two versions of the language
indefinitely.

The Python 3 statement was drawn up around 2016. Projects pledged to require
Python 3 by 2020, giving other projects confidence that they could plan a similar
transition, and allowing downstream users to figure out their options without a
nasty surprise. We didn't force people to move to Python 3, but if they wanted
to stick with Python 2, they would stop getting new versions of our projects.
The focus was originally on the scientific Python ecosystem, with Jupyter and
matplotlib among the first projects involved, but in late 2017 it was expanded
to any Python projects.
A rapidly growing number of projects signed up as we approached 2020.

The long-term transition we hoped for has succeeded: in 2024 it is entirely
normal for projects to support only Python 3, simplifying maintainers' lives
and letting us take full advantage of newer language features.
Copy link
Member

Choose a reason for hiding this comment

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

I would add a phrase along the lines of "without disrupting users still using Python 2 at the time" maybe ?

Thanks for writing this !

Copy link
Member Author

Choose a reason for hiding this comment

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

I've sort of mentioned this idea in the previous paragraph:

We didn't force people to move to Python 3, but if they wanted to stick with Python 2, they would stop getting new versions of our projects.

I don't want to over-sell this, because a) we wanted people in general to move to Python 3, even if Python 2 remained in some specific niches, to re-unify the Python world, and b) I'm sure the end of Python 2 support did disrupt people who needed/wanted to keep using it. Not our statement directly, but things like the removal of Python 2 from Linux distros, and the security concerns for anything that handles untrusted data. The python_requires stuff definitely helped to make things less painful, but it was never going to be totally disruption free.


Thank-you to all of the people, in projects big and small, who contributed
their support to the statement!