kennethreitz/python-guide
1
0
Fork 0
mirror of https://github.com/kennethreitz/python-guide.git synced 2026-06-05 14:50:19 +00:00
Code Issues Packages Projects Releases Wiki Activity

further clarification

Browse Source
This commit is contained in:
Kenneth Reitz
2016-11-26 19:19:14 -05:00
parent 0dc24a34e7
commit cfce3eac7a
1 changed files with 5 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/starting/which-python.rst
+5 -4
View File
@@ -25,11 +25,12 @@ I'll be blunt:
- Use Python 3 for new Python applications.
- If you're learning Python for the first time, familiarizing yourself with Python 2.7 will be very
useful, but not more useful than learning Python 3. Learn both. They are both "Python".
- Software that is already built (e.g. commercial software) often depends on Python 2.7.
useful, but not more useful than learning Python 3.
- Learn both. They are both "Python".
- Software that is already built often depends on Python 2.7.
- If you are writing a new open source Python library, it's best to write it for both Python 2 and 3
simultaneously. Supporting 3 only is a political statment and will alienate many of your users.
This is not a problem — slowly, over the next three years, this will become less the case.
simultaneously. Only supporting Python 3 for a new library you want to be widely adopted is a
political statment and will alienate many of your users. This is not a problem — slowly, over the next three years, this will become less the case.
So.... 3?
~~~~~~~~~