From e38561037d9c9697637f0af83e1a0fa628e7d310 Mon Sep 17 00:00:00 2001 From: Bruno Oliveira Date: Mon, 27 May 2019 19:25:33 -0300 Subject: [PATCH] Update docs about py27 and py34 support plans As discussed in #5275 --- doc/en/py27-py34-deprecation.rst | 22 +++++++++++++--------- 1 file changed, 13 insertions(+), 9 deletions(-) diff --git a/doc/en/py27-py34-deprecation.rst b/doc/en/py27-py34-deprecation.rst index 97d9abf83..95e96de04 100644 --- a/doc/en/py27-py34-deprecation.rst +++ b/doc/en/py27-py34-deprecation.rst @@ -7,16 +7,20 @@ Python 3.4's last release is scheduled for `March 2019 `__. pytest is one of the participating projects of the https://python3statement.org. -We plan to drop support for Python 2.7 and 3.4 at the same time with the release of **pytest 5.0**, -scheduled to be released by **mid-2019**. Thanks to the `python_requires `__ ``setuptools`` option, +The **pytest 4.6** series will be the last to support Python 2.7 and 3.4, and is scheduled +to be released by **mid-2019**. **pytest 5.0** and onwards will support only Python 3.5+. + +Thanks to the `python_requires`_ ``setuptools`` option, Python 2.7 and Python 3.4 users using a modern ``pip`` version -will install the last compatible pytest ``4.X`` version automatically even if ``5.0`` or later +will install the last pytest ``4.6`` version automatically even if ``5.0`` or later are available on PyPI. -During the period **from mid-2019 and 2020**, the pytest core team plans to make -bug-fix releases of the pytest ``4.X`` series by back-porting patches to the ``4.x-maintenance`` -branch. +While pytest ``5.0`` will be the new mainstream and development version, until **January 2020** +the pytest core team plans to make bug-fix releases of the pytest ``4.6`` series by +back-porting patches to the ``4.6-maintenance`` branch that affect Python 2 users. -**After 2020**, the core team will no longer actively back port-patches, but the ``4.x-maintenance`` -branch will continue to exist so the community itself can contribute patches. The -core team will be happy to accept those patches and make new ``4.X`` releases **until mid-2020**. +**After 2020**, the core team will no longer actively backport patches, but the ``4.6-maintenance`` +branch will continue to exist so the community itself can contribute patches. The core team will +be happy to accept those patches and make new ``4.6`` releases **until mid-2020**. + +.. _`python_requires`: https://packaging.python.org/guides/distributing-packages-using-setuptools/#python-requires>