Skip to content

Commit bf0133c

Browse files
author
Myke Cuthbert
committed
Accept three comments from @takluyver
1 parent ebe69ed commit bf0133c

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

_sections/20-statement.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -13,10 +13,10 @@ and techniques to maintain compatibility efficiently, it is a small but
1313
constant friction in the development of a lot of code.
1414

1515
We are keen to use Python 3 to its full potential, and though
16-
we had been accepting the
17-
cost of writing cross-compatible code to allow a smooth transition, we
16+
we accepted the cost of writing cross-compatible
17+
code to allow a smooth transition, we
1818
did not intend to maintain this compatibility indefinitely. Although the
19-
transition was not as quick as we hoped, it has taken place, with
19+
transition was not as quick as we hoped, it is taking place, with
2020
more and more people using, teaching and recommending Python 3.
2121

2222
The developers of the Python language extended support of Python 2.7 from 2015
@@ -35,6 +35,6 @@ if you enjoy the free, first party support for many projects including the Scien
3535
Python stack, please move to Python 3.
3636

3737
For all of these reasons, the following projects have pledged to **drop support
38-
for Python 2.7 no later than 2020**, coinciding with the Python development
39-
team's [drop of support for Python
40-
2.7 on January 1, 2020](https://www.python.org/dev/peps/pep-0373/#update).
38+
for Python 2.7 no later than 2020**, following the [end of support for Python
39+
2.7 itself](https://www.python.org/dev/peps/pep-0373/#update) at the start of
40+
the year.

0 commit comments

Comments
 (0)