From cfce3eac7a7ec91f29a3127636de7c75a7825a6e Mon Sep 17 00:00:00 2001 From: Kenneth Reitz Date: Sat, 26 Nov 2016 19:19:14 -0500 Subject: [PATCH] further clarification --- docs/starting/which-python.rst | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/docs/starting/which-python.rst b/docs/starting/which-python.rst index b8b5030..b8bf97c 100644 --- a/docs/starting/which-python.rst +++ b/docs/starting/which-python.rst @@ -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? ~~~~~~~~~