@@ -306,17 +306,19 @@ usually around 18 months between major releases.
|
306 | 306 | |
307 | 307 | The developers issue "bugfix" releases of older versions, so the stability of |
308 | 308 | existing releases gradually improves. Bugfix releases, indicated by a third |
309 | | -component of the version number (e.g. 2.5.3, 2.6.2), are managed for stability; |
| 309 | +component of the version number (e.g. 3.5.3, 3.6.2), are managed for stability; |
310 | 310 | only fixes for known problems are included in a bugfix release, and it's |
311 | 311 | guaranteed that interfaces will remain the same throughout a series of bugfix |
312 | 312 | releases. |
313 | 313 | |
314 | 314 | The latest stable releases can always be found on the `Python download page |
315 | | -<https://www.python.org/downloads/>`_. There are two recommended production-ready |
316 | | -versions at this point in time, because at the moment there are two branches of |
317 | | -stable releases: 2.x and 3.x. Python 3.x may be less useful than 2.x, since |
318 | | -currently there is more third party software available for Python 2 than for |
319 | | -Python 3. Python 2 code will generally not run unchanged in Python 3. |
| 315 | +<https://www.python.org/downloads/>`_. There are two production-ready version |
| 316 | +of Python: 2.x and 3.x, but the recommended one at this times is Python 3.x. |
| 317 | +Although Python 2.x is still widely used, `it will not be |
| 318 | +maintained after January 1, 2020 <https://www.python.org/dev/peps/pep-0373/>`_. |
| 319 | +Python 2.x was known for having more third-party libraries available, however, |
| 320 | +by the time of this writing, most of the widely used libraries support Python 3.x, |
| 321 | +and some are even dropping the Python 2.x support. |
320 | 322 | |
321 | 323 | |
322 | 324 | How many people are using Python? |
|