Skip to content

Commit eb16dcc

Browse files
committed
DOC: Add Python 2 statement to README, reference maintenance branch in CONTRIBUTING
1 parent 388f140 commit eb16dcc

File tree

2 files changed

+20
-0
lines changed

2 files changed

+20
-0
lines changed

CONTRIBUTING.md

+2
Original file line numberDiff line numberDiff line change
@@ -85,6 +85,8 @@ If you get no errors, you're ready to submit your changes!
8585
It's a good practice to create [a new branch](https://help.github.com/articles/about-branches/)
8686
of the repository for a new set of changes.
8787

88+
For Python 2.7-compatible fixes, the branch should start from the `maint/1.3.x` branch on the
89+
upstream repository.
8890

8991
**4. Submit a [pull request][link_pullrequest].**
9092

README.rst

+18
Original file line numberDiff line numberDiff line change
@@ -77,6 +77,24 @@ Information specific to Nipype is located here::
7777

7878
http://nipy.org/nipype
7979

80+
Python 2 Statement
81+
------------------
82+
83+
Python 2.7 reaches its end-of-life in January 2020, which means it will
84+
*no longer be maintained* by Python developers. `Many projects
85+
<https://python3statement.org/`__ are removing support in advance of this
86+
deadline, which will make it increasingly untenable to try to support
87+
Python 2, even if we wanted to.
88+
89+
The final series with 2.7 support is 1.3.x. If you have a package using
90+
Python 2 and are unable or unwilling to upgrade to Python 3, then you
91+
should use the following `dependency
92+
<https://www.python.org/dev/peps/pep-0440/#version-specifiers>`__ for
93+
Nipype::
94+
95+
nipype<1.4
96+
97+
Bug fixes will be accepted against the ``maint/1.3.x`` branch.
8098

8199
Support and Communication
82100
-------------------------

0 commit comments

Comments
 (0)