Skip to content

Commit bc49d6f

Browse files
authored
Update docs about py27 and py34 support plans (#5316)
Update docs about py27 and py34 support plans
2 parents e393a73 + e385610 commit bc49d6f

File tree

1 file changed

+13
-9
lines changed

1 file changed

+13
-9
lines changed

doc/en/py27-py34-deprecation.rst

Lines changed: 13 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -7,16 +7,20 @@ Python 3.4's last release is scheduled for
77
`March 2019 <https://www.python.org/dev/peps/pep-0429/#release-schedule>`__. pytest is one of
88
the participating projects of the https://python3statement.org.
99

10-
We plan to drop support for Python 2.7 and 3.4 at the same time with the release of **pytest 5.0**,
11-
scheduled to be released by **mid-2019**. Thanks to the `python_requires <https://packaging.python.org/guides/distributing-packages-using-setuptools/#python-requires>`__ ``setuptools`` option,
10+
The **pytest 4.6** series will be the last to support Python 2.7 and 3.4, and is scheduled
11+
to be released by **mid-2019**. **pytest 5.0** and onwards will support only Python 3.5+.
12+
13+
Thanks to the `python_requires`_ ``setuptools`` option,
1214
Python 2.7 and Python 3.4 users using a modern ``pip`` version
13-
will install the last compatible pytest ``4.X`` version automatically even if ``5.0`` or later
15+
will install the last pytest ``4.6`` version automatically even if ``5.0`` or later
1416
are available on PyPI.
1517

16-
During the period **from mid-2019 and 2020**, the pytest core team plans to make
17-
bug-fix releases of the pytest ``4.X`` series by back-porting patches to the ``4.x-maintenance``
18-
branch.
18+
While pytest ``5.0`` will be the new mainstream and development version, until **January 2020**
19+
the pytest core team plans to make bug-fix releases of the pytest ``4.6`` series by
20+
back-porting patches to the ``4.6-maintenance`` branch that affect Python 2 users.
21+
22+
**After 2020**, the core team will no longer actively backport patches, but the ``4.6-maintenance``
23+
branch will continue to exist so the community itself can contribute patches. The core team will
24+
be happy to accept those patches and make new ``4.6`` releases **until mid-2020**.
1925

20-
**After 2020**, the core team will no longer actively back port-patches, but the ``4.x-maintenance``
21-
branch will continue to exist so the community itself can contribute patches. The
22-
core team will be happy to accept those patches and make new ``4.X`` releases **until mid-2020**.
26+
.. _`python_requires`: https://packaging.python.org/guides/distributing-packages-using-setuptools/#python-requires>

0 commit comments

Comments
 (0)