Skip to content

Tweak wording to be a bit more obvious about certain things #6

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 1 commit into from
May 11, 2016
Merged

Tweak wording to be a bit more obvious about certain things #6

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
19 changes: 10 additions & 9 deletions _sections/20-statement.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,18 +17,19 @@ two versions of the language for several years. While we have developed tools
and techniques to maintain compatibility efficiently, it is a small but
constant friction in the development of a lot of code.

We are keen to use Python 3, and we currently accept the cost of writing
cross-compatible code to allow a smooth transition, but we don’t intend to
maintain this indefinitely. Although the transition has not been as quick as we
hoped, we do see it taking place, with more and more people using, teaching and
recommending Python 3.
We are keen to use Python 3 to its full potential, and we currently accept the
cost of writing cross-compatible code to allow a smooth transition, but we
don’t intend to maintain this compatibility indefinitely. Although the
transition has not been as quick as we hoped, we do see it taking place, with
more and more people using, teaching and recommending Python 3.

The developers of the Python language extended support of Python 2.7 from 2015
to 2020, recognising that many people were still using Python 2. We believe
that the extra 5 years is sufficient, and our projects plan to stop supporting
Python 2 when upstream support ends in 2020, if not before. We will then be
able to simplify our code and take advantage of the many new features in the
current version of the Python language and standard library.
that the extra 5 years is sufficient to transition off of Python 2, and our
projects plan to stop supporting Python 2 when upstream support ends in 2020,
if not before. We will then be able to simplify our code and take advantage of
the many new features in the current version of the Python language and
standard library.

In addition, significantly before 2020, some of our projects will step down
Python 2.7 support to only fixing bugs, and make new feature releases which
Expand Down