Skip to content

Commit 1859bc5

Browse files
committed
update 2 or 3 page
1 parent 08ba2ab commit 1859bc5

File tree

1 file changed

+16
-12
lines changed

1 file changed

+16
-12
lines changed

content/pages/01-introduction/04-python-2-or-3.markdown

Lines changed: 16 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -14,25 +14,25 @@ questions about which version they should learn. It is confusing to hear
1414
that Python 3, which was originally released in 2008, is still not the default
1515
installation on some operating systems.
1616

17-
Here's the good news: you can't go wrong starting with either version. While
18-
there are differences in unicode and syntax, for the most part if you
19-
start with Python 2 and then learn Python 3 you won't be starting from
20-
scratch. Likewise, you'll be able to read and write Python 2 code if you
21-
started with Python 3.
22-
23-
That said, my personal recommendation for new programmers as of right
24-
now is to use Python 3, specifically 3.6 as of January 2017. There are
17+
The simple answer is: learn Python 3, specifically the latest version
18+
which as of May 2018 is [Python 3.6.5](https://www.python.org/downloads/).
19+
If for some reason you absolutely have to learn Python 2, for example because
20+
your employer is working on a bunch of legacy code, you will be able to
21+
transfer the majority of your knowledge from Python 2 right into Python 3.
22+
Likewise, you will still be able to read and write Python 2 code if you
23+
start with Python 3.
24+
25+
In addition, my personal strong recommendation for new programmers as of
26+
right now is to use Python 3. There are
2527
enough [great resources](/best-python-resources.html)
2628
out there that teach version 3 from the ground up. Python 3 is the future
2729
and you will not regret starting with the latest version of the
2830
programming language.
2931

3032
However, if you are interested in DevOps-type work with
3133
[configuration management tools](/configuration-management.html) such as
32-
Ansible or Fabric, then you'll have to stick to Python 2 because they have
33-
yet to upgrade to support Python 3. If you know there are libraries you must
34-
use in a project, check the
35-
[Python Walls of Superpowers](https://python3wos.appspot.com/).
34+
[Fabric](http://www.fabfile.org/), then you may have to use both Python 2
35+
and 3 because some of the libraries are lagging in full Python support.
3636

3737

3838
### Visualizations and Projects
@@ -81,6 +81,10 @@ gone through the process and have advice for making it less painful.
8181
deploying the new version before going back to clean up unnecessary code
8282
created by the transition.
8383

84+
* [he only problem with Python 3's str is that you don't grok it](http://sircmpwn.github.io/2017/01/13/The-problem-with-Python-3.html)
85+
specifically covers strings and some of the misconceptions around
86+
how strings are handled in version 2 versus version 3.
87+
8488

8589
### Python 2 to 3 resources
8690
* [Why should I use Python 3?](https://eev.ee/blog/2016/07/31/python-faq-why-should-i-use-python-3/)

0 commit comments

Comments
 (0)