This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Title: Python2 or Python3 page
Type: Stage:
Components: Documentation Versions: Python 3.2, Python 3.3
Status: closed Resolution: not a bug
Dependencies: Superseder:
Assigned To: docs@python Nosy List: JBernardo, docs@python, pitrou, terry.reedy
Priority: normal Keywords:

Created on 2011-08-13 02:35 by JBernardo, last changed 2022-04-11 14:57 by admin. This issue is now closed.

Messages (3)
msg142004 - (view) Author: João Bernardo (JBernardo) * Date: 2011-08-13 02:35
Since 2008 (as far as can remember) the Python Download page has a link to that web page:

I know it's been updated but it keeps saying the same thing since Python 3.0 was launched.

Basically it says that Python 3 is awesome but please don't use it because not everything became compatible. (That's how a newcomer reads it).

I've been using Python 3 as replacement of Python 2 since the launch of 3.1... And now I can't even write a Python 2 code without feeling a little sick.

I pretty much think it's time to tell people to skip learning all that junk the dev team had to remove and start with something much nicer.

Think about it. You'll not have to worry if list comprehensions/generator expressions are available, the conditional operator, the boolean type (and True and False as keywords), decorators, the ability of having `non local` variables, extended tuple unpacking etc etc etc.

If nobody uses the next generation of the language, the developers won't port their code. If they don't port the code, no one can use it...


So I vote for a new page saying something like "Python 3 is the way you should go and, if you can't run something, try asking the developer to port it or choose another tool"

BTW, Those PyPI modules that haven't made any effort to port should be marked as `deprecated`, but that doesn't have anything to do with the change of the aforementioned web page.

Sorry if that doesn't belong to a bug report and erase it if you want.
msg142027 - (view) Author: Antoine Pitrou (pitrou) * (Python committer) Date: 2011-08-13 16:40
It is a wiki page, so you can edit it yourself (you probably need to register, though).
If you think your modifications would be too drastic, perhaps you want to launch a discussion on the python-dev mailing-list about that page and its current contents.
msg142494 - (view) Author: Terry J. Reedy (terry.reedy) * (Python committer) Date: 2011-08-19 20:24
I agree with your sentiments about Python 2 while being aware that not all agree yet and that the current Wiki page was the result of some heated discussion and compromise. I also agree that the page could use tweaking/updating/rewriting. For one thing the supposed 2010 date in inconsistent with 3.2 being released.

"Python 3 is the future of the language." kind of implies that it is not the current version of the language. I would change that to "Python 3 is the present and future of the language"

I might start with discussion of 3 rather that 2.

I am closing this simply because it is not about changing the CPython repository, which is what the tracker tracks. There is no way to attach and review a wiki diff here.
Date User Action Args
2022-04-11 14:57:20adminsetgithub: 56954
2011-08-19 20:24:46terry.reedysetstatus: open -> closed

nosy: + terry.reedy
messages: + msg142494

resolution: not a bug
2011-08-13 16:40:50pitrousetnosy: + pitrou
messages: + msg142027
2011-08-13 02:35:55JBernardocreate