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

Remove Python 2.6 support. #630

Merged
merged 5 commits into from
Sep 16, 2015
Merged

Remove Python 2.6 support. #630

merged 5 commits into from
Sep 16, 2015

Conversation

jsha
Copy link
Contributor

@jsha jsha commented Jul 23, 2015

Fixes #515

cc @kuba because I know you've done a lot of work on maintaining the py26 support up to this point. I you haven't seen it yet, check out my comment on #515.

@schoen
Copy link
Contributor

schoen commented Jul 23, 2015

Looks good to me, though I don't know whether there will prove to be any other things that also need to be removed (or dependencies that could now be removed as a result of this change).

@kuba
Copy link
Contributor

kuba commented Jul 23, 2015 via email

@jsha
Copy link
Contributor Author

jsha commented Jul 23, 2015

Talking with James, Brad, and Seth, it sounds like Python 2.6 support has been a small but persistent backwards pull on their development time. I think it's safe to say team members mostly develop on Python 2.7, and then discover Python 2.6 regressions when running final cross-platform tests for submission. That sometimes involves going back and changing code to be Python 2.7 compatible.

With launch coming up in eight weeks, we really need to remove all stumbling blocks in the way of making fast forward progress. I think the work Python 2.6 generates vs the benefit I expect it to get us argues strongly in favor of cutting it. Like I said in #515, we'll be able to get much better data after launch, as we find out how many people want to use Let's Encrypt but are stymied by lack of Python 2.6 support.

@jsha
Copy link
Contributor Author

jsha commented Aug 6, 2015

Updated to remove py3+ as well, since the py3 tests are breaking in #653.

@bmw
Copy link
Member

bmw commented Aug 6, 2015

LGTM!

pde added a commit that referenced this pull request Sep 16, 2015
@pde pde merged commit e224a2e into master Sep 16, 2015
@pde
Copy link
Member

pde commented Sep 16, 2015

Merged for now; we can reenable python 2.6 support once we're in good launched shape!

@pde pde deleted the rm-py26 branch September 16, 2015 01:53
@pde pde restored the rm-py26 branch September 16, 2015 02:01
@pde
Copy link
Member

pde commented Sep 16, 2015

(Also disabling tox for these Python versions, which will sometimes mean faster turnarounds from Travis)

@kuba
Copy link
Contributor

kuba commented Sep 16, 2015

Urm...... #704

@@ -40,7 +40,6 @@ commands =
./tox.cover.sh

[testenv:lint]
# recent versions of pylint do not support Python 2.6 (#97, #187)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

could we please not remove this comment? I'm gonna have really hard times tracking this back when py 2.6 support will be back...

@kuba kuba mentioned this pull request Oct 12, 2015
kuba added a commit that referenced this pull request Jan 9, 2016
Despite its description,
#630, removed not only
Python 2.6 support, but also Travis tests against Python 3. ACME
library supports Python 3 and Travis should tests it.

This must be merged before any pending PRs agains acme library.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants