-
Notifications
You must be signed in to change notification settings - Fork 292
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
Drop Python 3.3 support #357
Comments
Thank you for writing this up with all the relevant links and information--that helps a ton! I'm game for dropping support for Python 3.3. I'll add it to the 1.0 milestone. If someone has a compelling reason not to drop Python 3.3, please add a comment. |
Historically the viewpoint I've taken is given we're vendored into pip we should support the same set of versions as pip does (to avoid any need for pip to fork html5lib). |
Wow--I had no idea html5lib-python was vendored in pip. That's... interesting. @gsnedders How do we figure out what versions of pip are supported? Are we just checking their current release to see what versions of Python it supports? For example, master tip still supports Python 3.3: https://github.com/pypa/pip/blob/3998df351853c68274802502fead7607c8ab8eeb/setup.py#L54 |
I think it makes sense for pip to vendor things, it needs to be able to install from a download with maybe no external net access except an internal PyPI server. Here's the pip decision and PR to deprecate 3.3 in the next pip 10 and drop it in pip 11. Their latest stable docs say 2.6, 2.7, 3.3-3.5, pypy. Latest master says 2.7, 3.3-3.6, pypy. |
That makes sense! Seems like we shouldn't drop support for 3.3 in html5lib-python 1.0. Beyond that, I'll leave this until you get pinged and we can drop it. |
Is there any interest in dropping support for EOL Python 3.3?
Here's the pip installs from PyPI for the last month, showing low demand for 3.3:
The text was updated successfully, but these errors were encountered: