@@ -17,18 +17,19 @@ two versions of the language for several years. While we have developed tools
1717and techniques to maintain compatibility efficiently, it is a small but
1818constant friction in the development of a lot of code.
1919
20- We are keen to use Python 3, and we currently accept the cost of writing
21- cross-compatible code to allow a smooth transition, but we don’t intend to
22- maintain this indefinitely. Although the transition has not been as quick as we
23- hoped, we do see it taking place, with more and more people using, teaching and
24- recommending Python 3.
20+ We are keen to use Python 3 to its full potential , and we currently accept the
21+ cost of writing cross-compatible code to allow a smooth transition, but we
22+ don’t intend to maintain thiscompatibility indefinitely. Although the
23+ transition has not been as quick as we hoped, we do see it taking place, with
24+ more and more people using, teaching and recommending Python 3.
2525
2626The developers of the Python language extended support of Python 2.7 from 2015
2727to 2020, recognising that many people were still using Python 2. We believe
28- that the extra 5 years is sufficient, and our projects plan to stop supporting
29- Python 2 when upstream support ends in 2020, if not before. We will then be
30- able to simplify our code and take advantage of the many new features in the
31- current version of the Python language and standard library.
28+ that the extra 5 years is sufficient to transition off of Python 2, and our
29+ projects plan to stop supporting Python 2 when upstream support ends in 2020,
30+ if not before. We will then be able to simplify our code and take advantage of
31+ the many new features in the current version of the Python language and
32+ standard library.
3233
3334In addition, significantly before 2020, some of our projects will step down
3435Python 2.7 support to only fixing bugs, and make new feature releases which