new python 2 or 3 resources

mattmakai · mattmakai · commit ba9a4f316cf4 · 2017-01-04T10:01:38.000-08:00
diff --git a/all.html b/all.html
@@ -223,18 +223,19 @@ <h3>More perspectives on why to use Python</h3>
           <h1>Python 2 or 3?</h1>
 <p>The Python programming language is currently in the midst of a long-term
 transition from version 2 to version 3. New programmers typically have many
-questions about which version they should learn. It's confusing to hear
+questions about which version they should learn. It is confusing to hear
 that Python 3, which was originally released in 2008, is still not the default
-installation on many operating systems.</p>
+installation on some operating systems.</p>
 <p>Here's the good news: you can't go wrong starting with either version. While 
 there are differences in unicode and syntax, for the most part if you 
 start with Python 2 and then learn Python 3 you won't be starting from 
 scratch. Likewise, you'll be able to read and write Python 2 code if you 
 started with Python 3.</p>
-<p>My personal recommendation for new programmers as of right now is to use
-Python 3. There are enough <a href="/best-python-resources.html">great resources</a>
+<p>That said, my personal recommendation for new programmers as of right 
+now is to use Python 3, specifically 3.6 as of January 2017. There are 
+enough <a href="/best-python-resources.html">great resources</a>
 out there that teach version 3 from the ground up. Python 3 is the future
-and you will not regret starting with the "correct" version of the
+and you will not regret starting with the latest version of the
 programming language.</p>
 <p>However, if you are interested in DevOps-type work with 
 <a href="/configuration-management.html">configuration management tools</a> such as 
@@ -291,6 +292,13 @@ <h3>Porting to Python 3 resources</h3>
   is a screencast showing how to run both Python 2 and 3 for different
   projects using pyenv.</p>
 </li>
+<li>
+<p><a href="https://tech.yplanapp.com/2016/08/24/upgrading-to-python-3-with-zero-downtime/">Upgrading to Python 3 with Zero Downtime</a>
+  supplies advice on transitioning a large existing Python 2 web application 
+  to Python 3. Their process involved upgrading dependencies, testing and
+  deploying the new version before going back to clean up unnecessary code
+  created by the transition.</p>
+</li>
 </ul>
 <h3>Python 2 to 3 resources</h3>
 <ul>
@@ -347,6 +355,12 @@ <h3>Python 2 to 3 resources</h3>
   strongly encourages Python 3 adoption by publicly stating their
   intentions. </p>
 </li>
+<li>
+<p>Only 28% of dependencies still only support Python 2, according to 
+  <a href="https://medium.com/broken-window/python-3-support-for-third-party-libraries-dcd7a156e5bd">this post's analysis of 6000 Python libraries</a>.
+  The other 72% of libraries either support both Python 2 &amp; 3 (14%), or only 
+  support Python 3 (58%).</p>
+</li>
 </ul>
           <h1>Enterprise Python</h1>
 <p>One of the misconceptions around Python and other dynamically-typed languages 
@@ -9848,6 +9862,7 @@ <h1>Change Log</h1>
 <h2>2017</h2>
 <h3>January</h3>
 <ul>
+<li>Added new resources to the <a href="/python-2-or-3.html">Python 2 or 3?</a> page.</li>
 <li>Fixed all 404 link rot on every page. However, if a page has been rewritten
   or redirected and is no longer valuable as a link, please 
   <a href="https://twitter.com/fullstackpython">tweet me</a> or 
diff --git a/change-log.html b/change-log.html
@@ -43,6 +43,7 @@ <h1>Change Log</h1>
 <h2>2017</h2>
 <h3>January</h3>
 <ul>
+<li>Added new resources to the <a href="/python-2-or-3.html">Python 2 or 3?</a> page.</li>
 <li>Fixed all 404 link rot on every page. However, if a page has been rewritten
   or redirected and is no longer valuable as a link, please 
   <a href="https://twitter.com/fullstackpython">tweet me</a> or 
diff --git a/python-2-or-3.html b/python-2-or-3.html
@@ -46,18 +46,19 @@
           <h1>Python 2 or 3?</h1>
 <p>The Python programming language is currently in the midst of a long-term
 transition from version 2 to version 3. New programmers typically have many
-questions about which version they should learn. It's confusing to hear
+questions about which version they should learn. It is confusing to hear
 that Python 3, which was originally released in 2008, is still not the default
-installation on many operating systems.</p>
+installation on some operating systems.</p>
 <p>Here's the good news: you can't go wrong starting with either version. While 
 there are differences in unicode and syntax, for the most part if you 
 start with Python 2 and then learn Python 3 you won't be starting from 
 scratch. Likewise, you'll be able to read and write Python 2 code if you 
 started with Python 3.</p>
-<p>My personal recommendation for new programmers as of right now is to use
-Python 3. There are enough <a href="/best-python-resources.html">great resources</a>
+<p>That said, my personal recommendation for new programmers as of right 
+now is to use Python 3, specifically 3.6 as of January 2017. There are 
+enough <a href="/best-python-resources.html">great resources</a>
 out there that teach version 3 from the ground up. Python 3 is the future
-and you will not regret starting with the "correct" version of the
+and you will not regret starting with the latest version of the
 programming language.</p>
 <p>However, if you are interested in DevOps-type work with 
 <a href="/configuration-management.html">configuration management tools</a> such as 
@@ -114,6 +115,13 @@ <h3>Porting to Python 3 resources</h3>
   is a screencast showing how to run both Python 2 and 3 for different
   projects using pyenv.</p>
 </li>
+<li>
+<p><a href="https://tech.yplanapp.com/2016/08/24/upgrading-to-python-3-with-zero-downtime/">Upgrading to Python 3 with Zero Downtime</a>
+  supplies advice on transitioning a large existing Python 2 web application 
+  to Python 3. Their process involved upgrading dependencies, testing and
+  deploying the new version before going back to clean up unnecessary code
+  created by the transition.</p>
+</li>
 </ul>
 <h3>Python 2 to 3 resources</h3>
 <ul>
@@ -170,6 +178,12 @@ <h3>Python 2 to 3 resources</h3>
   strongly encourages Python 3 adoption by publicly stating their
   intentions. </p>
 </li>
+<li>
+<p>Only 28% of dependencies still only support Python 2, according to 
+  <a href="https://medium.com/broken-window/python-3-support-for-third-party-libraries-dcd7a156e5bd">this post's analysis of 6000 Python libraries</a>.
+  The other 72% of libraries either support both Python 2 &amp; 3 (14%), or only 
+  support Python 3 (58%).</p>
+</li>
 </ul>
 <h3>What's next now that you know about Python versions?</h3>
 <div class="row">
diff --git a/source/content/pages/01-introduction/04-python-2-or-3.markdown b/source/content/pages/01-introduction/04-python-2-or-3.markdown
@@ -10,20 +10,21 @@ meta: Learn about whether you should use Python version 2 or 3 to build your app
 # Python 2 or 3?
 The Python programming language is currently in the midst of a long-term
 transition from version 2 to version 3. New programmers typically have many
-questions about which version they should learn. It's confusing to hear
+questions about which version they should learn. It is confusing to hear
 that Python 3, which was originally released in 2008, is still not the default
-installation on many operating systems.
+installation on some operating systems.
 
 Here's the good news: you can't go wrong starting with either version. While 
 there are differences in unicode and syntax, for the most part if you 
 start with Python 2 and then learn Python 3 you won't be starting from 
 scratch. Likewise, you'll be able to read and write Python 2 code if you 
 started with Python 3.
 
-My personal recommendation for new programmers as of right now is to use
-Python 3. There are enough [great resources](/best-python-resources.html)
+That said, my personal recommendation for new programmers as of right 
+now is to use Python 3, specifically 3.6 as of January 2017. There are 
+enough [great resources](/best-python-resources.html)
 out there that teach version 3 from the ground up. Python 3 is the future
-and you will not regret starting with the "correct" version of the
+and you will not regret starting with the latest version of the
 programming language.
 
 However, if you are interested in DevOps-type work with 
@@ -76,6 +77,12 @@ gone through the process and have advice for making it less painful.
   is a screencast showing how to run both Python 2 and 3 for different
   projects using pyenv.
 
+* [Upgrading to Python 3 with Zero Downtime](https://tech.yplanapp.com/2016/08/24/upgrading-to-python-3-with-zero-downtime/)
+  supplies advice on transitioning a large existing Python 2 web application 
+  to Python 3. Their process involved upgrading dependencies, testing and
+  deploying the new version before going back to clean up unnecessary code
+  created by the transition.
+
 
 ### Python 2 to 3 resources
 * [Why should I use Python 3?](https://eev.ee/blog/2016/07/31/python-faq-why-should-i-use-python-3/)
@@ -122,3 +129,8 @@ gone through the process and have advice for making it less painful.
   strongly encourages Python 3 adoption by publicly stating their
   intentions. 
 
+* Only 28% of dependencies still only support Python 2, according to 
+  [this post's analysis of 6000 Python libraries](https://medium.com/broken-window/python-3-support-for-third-party-libraries-dcd7a156e5bd).
+  The other 72% of libraries either support both Python 2 & 3 (14%), or only 
+  support Python 3 (58%).
+
diff --git a/source/content/pages/12-meta/01-change-log.markdown b/source/content/pages/12-meta/01-change-log.markdown
@@ -15,6 +15,7 @@ inception in December 2012. You can view detailed changes via the
 
 ## 2017
 ### January
+* Added new resources to the [Python 2 or 3?](/python-2-or-3.html) page.
 * Fixed all 404 link rot on every page. However, if a page has been rewritten
   or redirected and is no longer valuable as a link, please 
   [tweet me](https://twitter.com/fullstackpython) or 
