bpo-34203: FAQ: minor additional rewording and fix a few typos #9821
Conversation
This is following up the recent change to this section recommending 3.x over 2.x.
taleinat
changed the title
Doc/faq/general.rst
Outdated
| of Python: 2.x and 3.x, with the recommended one at this time being 3.x. | ||
| Although 2.x is still widely used, `it will not be maintained after | ||
| January 1, 2020 <https://www.python.org/dev/peps/pep-0373/>`_. 2.x was known | ||
| for having more third-party libraries available; however, by the time of this |
There was a problem hiding this comment.
If you keep this, I would make it "at the time of this".
Doc/faq/general.rst
Outdated
| <https://www.python.org/downloads/>`_. There are two production-ready versions | ||
| of Python: 2.x and 3.x, with the recommended one at this time being 3.x. | ||
| Although 2.x is still widely used, `it will not be maintained after | ||
| January 1, 2020 <https://www.python.org/dev/peps/pep-0373/>`_. 2.x was known |
There was a problem hiding this comment.
I think I'd drop the historical "2.x used to be better" wording, and just make this "Python 3.x is supported by most widely used libraries".
Doc/faq/general.rst
Outdated
| by the time of this writing, most of the widely used libraries support Python 3.x, | ||
| and some are even dropping the Python 2.x support. | ||
| <https://www.python.org/downloads/>`_. There are two production-ready versions | ||
| of Python: 2.x and 3.x, with the recommended one at this time being 3.x. |
There was a problem hiding this comment.
Instead of 'at this time', you could consider 'as of October 2018', as that clarifies the time at which the text was written. Although it's also fair to assume that the recommendation will be valid until the rest of the text is also rewritten. (same for the 'at this time' at line 319)
There was a problem hiding this comment.
We could also just drop "at this time", since the recommended version is going to be 3.x in the foreseeable future.
|
I removed the " needs backport to 3.6" label, the 3.6 branch no longer accept bugfixes (only security fixes are accepted): https://devguide.python.org/#status-of-python-branches |
|
@taleinat This is a good improvement over the current wording. In the last comment you mentioned dropping 'at this time', which I agree with. It would be great if this could be merged soon. :-) |
|
I've updated the wording following the comments here. |
|
Thanks @taleinat for the PR 🌮🎉.. I'm working now to backport this PR to: 2.7, 3.7. |
|
GH-12567 is a backport of this pull request to the 3.7 branch. |
|
GH-12568 is a backport of this pull request to the 2.7 branch. |
…H-9821) (GH-12568) (cherry picked from commit 6cd658b) Co-authored-by: Tal Einat <taleinat+github@gmail.com> https://bugs.python.org/issue34203
This is following up @augustogoulart's recent change to the "How stable is Python?" FAQ section, recommending 3.x over 2.x.
Upon reading the final build version, I noticed a few typos and an over-abundant use of the name "Python". This is a minor revision fixing those issues.
https://bugs.python.org/issue34203