|
| 1 | +--- |
| 2 | +title: archive |
| 3 | +bg: 'white' |
| 4 | +--- |
| 5 | + |
| 6 | +# History |
| 7 | + |
| 8 | +This page is now an archive of part of the transition from Python 2 to 3. |
| 9 | + |
| 10 | +By around 2015, when Python 2 support was originally planned to end, many |
| 11 | +important Python libraries and tools supported Python 3. But Python 2 still had |
| 12 | +a lot of users, and projects needed to support both major versions. The end of |
| 13 | +Python 2 support was postponed to 2020, and some people argued that development |
| 14 | +of Python 2 should resume. It seemed like a real possibility that the end date |
| 15 | +would be postponed again, and we'd need to support two versions of the language |
| 16 | +indefinitely. |
| 17 | + |
| 18 | +The Python 3 statement was drawn up around 2016. Projects pledged to require |
| 19 | +Python 3 by 2020, giving other projects confidence that they could plan a similar |
| 20 | +transition, and allowing downstream users to figure out their options without a |
| 21 | +nasty surprise. We didn't force people to move to Python 3, but if they wanted |
| 22 | +to stick with Python 2, they would stop getting new versions of our projects. |
| 23 | +The focus was originally on the scientific Python ecosystem, with Jupyter and |
| 24 | +matplotlib among the first projects involved, but in late 2017 it was expanded |
| 25 | +to any Python projects. |
| 26 | +A rapidly growing number of projects signed up as we approached 2020. |
| 27 | + |
| 28 | +The long-term transition we hoped for has succeeded: in 2024 it is entirely |
| 29 | +normal for projects to support only Python 3, simplifying maintainers' lives |
| 30 | +and letting us take full advantage of newer language features. |
| 31 | + |
| 32 | +Thank-you to all of the people, in projects big and small, who contributed |
| 33 | +their support to the statement! |
0 commit comments