-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Stop testing Python 3.3 in Travis #1372
Conversation
This is already done in #1342 and is deferred to the next major release. If installing |
Actually, my bad, it looks like I think it's time to land #1342. |
I talked to @jaraco about this at the PyCon sprint earlier this morning, and our tentative plan was:
Would you like to handle this differently? We could immediately merge #1342 and go straight to 40.0.0, just thought it would be nice to make the latest fixes available to any remaining Python 3.3 users before doing that. |
Hm, this is a tiny bit complicated. I was hoping that we could just pin wheel at 0.30.0 until the 40.0.0 release (and just revert the single commit that does that), but it seems there are some more complicated dependencies in the test suite. |
Eh, #1373 seems like it's not quite working and I don't think it's worth being fiddly about. This approach works fine. |
Latest setuptools does not support anymore Python 3.3 pypa/setuptools#1372
Latest setuptools does not support anymore Python 3.3 pypa/setuptools#1372
Summary of changes
The Python 3.3 job in Travis failed in the last build on master because the new
wheel
release won't install on it. We planned on dropping 3.3 support soon anyway, so just stop testing it on Travis to avoid further job failures. We'll release one more version that officially supports Python 3.3 while incorporating all the latest fixes from master, and then the next one will fully remove support for it.Pull Request Checklist