Skip to content

Commit c769b54

Browse files
committed
rewrite of 3 vs 2
1 parent 521bcda commit c769b54

File tree

1 file changed

+11
-18
lines changed

1 file changed

+11
-18
lines changed

docs/starting/which-python.rst

Lines changed: 11 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -13,10 +13,11 @@ one might think.
1313

1414
The basic gist of the state of things is as follows:
1515

16-
1. Python 2.7 has been the standard for a *long* time.
17-
2. Python 3 introduced major changes to the language, which many developers are unhappy with.
18-
3. Python 2.7 will receive necessary security updates until 2020 [#pep373_eol]_.
16+
1. Python 2.7 has been the standard for a *long* time, and is being officially deprecated `in 2020 <https://pythonclock.org>`_.
17+
2. Python 3 introduced major changes to the language, which have taken some time for the community to adjust to.
18+
3. As menitoned, Python 2.7 will only receive necessary security updates until 2020 [#pep373_eol]_.
1919
4. Python 3 is continually evolving, like Python 2 did in years past.
20+
5. The brand name "Python" encapsulates both Python 3 and Python 2.
2021

2122
So, you can now see why this is not such an easy decision.
2223

@@ -26,21 +27,13 @@ Recommendations
2627

2728
I'll be blunt:
2829

29-
30-
**Use Python 3 if...**
31-
32-
- You don't care.
33-
- You love Python 3.
34-
- You are indifferent towards 2 vs 3.
35-
- You don't know which one to use.
36-
- You embrace change.
37-
38-
**Use Python 2 if...**
39-
40-
- You love Python 2 and are saddened by the future being Python 3.
41-
- The stability requirements of your software would be improved by a language and runtime that never changes.
42-
- Software that you depend on requires it.
43-
30+
- Use Python 3 for new Python applications.
31+
- If you're learning Python for the first time, familiarizing yourself with Python 2.7 will be very
32+
useful, but not more useful than learning Python 3. Learn both. They are both "Python".
33+
- Software that is already built (e.g. commercial software) often depends on Python 2.7.
34+
- If you are writing a new open source Python library, it's best to write it for both Python 2 and 3
35+
simultaneously. Supporting 3 only is a political statment and will alienate many of your users.
36+
This is not a problem — slowly, over the next three years, this will become less the case.
4437

4538
So.... 3?
4639
~~~~~~~~~

0 commit comments

Comments
 (0)