Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Python 2 statement #498

Merged
merged 2 commits into from
Feb 10, 2019
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions docs/index.rst
Original file line number Diff line number Diff line change
Expand Up @@ -60,6 +60,7 @@ Day-to-Day Usage

license
backward-compatibility
python-2
contributing
changelog

Expand Down
25 changes: 25 additions & 0 deletions docs/python-2.rst
Original file line number Diff line number Diff line change
@@ -0,0 +1,25 @@
Python 2 Statement
==================

While ``attrs`` has always been a Python 3-first package, we the maintainers are aware that Python 2 will not magically disappear in 2020.
We are also aware that ``attrs`` is an important building block in many people's systems and livelihoods.

As such, we do **not** have any immediate plans to drop Python 2 support in ``attrs``.
We intend to support is as long as it will be technically feasible for us.

Feasibility in this case means:

1. Possibility to run the tests on our development computers,
2. and **free** CI options.

This can mean that we will have to run our tests on PyPy, whose maintainters have unequivocally declared that they do not intend to stop the development and maintenance of their Python 2-compatible line at all.
And this can mean that at some point, a sponsor will have to step up and pay for bespoke CI setups.

**However**: there is no promise of new features coming to ``attrs`` running under Python 2.
It is up to our discretion alone, to decide whether the introduced complexity or awkwardness are worth it, or whether we choose to make a feature available on modern platforms only.


Summary
-------

We will do our best to support existing users, but nobody is entitled to the latest and greatest features on a platform that is officially end of life.