Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

What should the Python support level going forward be in html5lib?#561

ambv started this conversation inPolls
Discussion options

ambv
Mar 1, 2023
Maintainer

Python 2.7 has been EOL since April 2020.
Python 3.5 has been EOL since September 2020.
Python 3.6 has been EOL since September 2021.
Python 3.7 is going away in June 2023.

Python 3.5 and 3.6 are no longer available on GitHub Actions for CI purposes.

Dropping Python 2 would allow us to stop worrying about narrow builds and usepathlib. Adopting "3.6+" would allow us to use f-strings. Adopting "3.7+" would let us coverhtml5lib with typing annotations and enable type checking.

What should the Python support level going forward be in html5lib?
2.7, 3.5+
0%
2.7, 3.6+
0%
2.7, 3.7+
0%
3.5+
0%
3.6+
6%
3.7+
46%
3.8+
46%

15 votes

You must be logged in to vote

Replies: 4 comments 3 replies

Comment options

FWIW: historically I believe the baseline was "whatever pip requires" plus "whatever web-platform-tests requires" (the latter mostly because… it was as a dependency of that which essentially got maintenance work done), where the former seems to be 3.7 and the latter seems to be 3.6 for now (mostly due to the Firefox tooling:https://bugzilla.mozilla.org/show_bug.cgi?id=1734402, because Ubuntu and other distros want to be able to build with their packaged and maintained Python version)

You must be logged in to vote
3 replies
@ambv
Comment options

ambvMar 3, 2023
Maintainer Author

Two additional advantages of going 3.7+ would be that we could usedataclasses and with type annotations and dataclasses we could adoptmypyc to compile the library. Black compiled with mypyc goes 2X as fast as vanilla Python. That's better than what Cython can give us because mypyc supports a subset of Python with some shortcuts in object attribute access, among others.

@ambv
Comment options

ambvMar 3, 2023
Maintainer Author

Another advantage: we could drop AppVeyor entirely and rely on just GitHub Actions which is much faster and better integrated with GitHub.

@gsnedders
Comment options

Given the Mozilla bug just got closed with them moving to Python 3.7 (presumably as ToT is going to releaseafter Ubuntu 18.04 LTS goes out of LTS support)… I guess that makes this clearly 3.7 now?

I do agree with need to reach a point of 3.7, the only question was quite how soon we could do that—though it clearly wasn't far off.

Comment options

ambv
Mar 10, 2023
Maintainer Author

OK. The consensus is to release 1.2 with support for 2.7 - 3.11, and immediately after cut support for 2.7, 3.5, and 3.6.

You must be logged in to vote
0 replies
Comment options

I have been having trouble with the Django Rest framework dependency on html5lib for some time. Although I was apparently able to install "sudo apt -y install python3-html5lib", I still get an import error when I attempt to install restframework: "cannot import name 'html5lib' from 'pip._vendor' (/usr/lib/python3/dist-packages/pip/_vendor/init.py)". Any thoughts or suggestions for me? thx,pete.godston@gmail.com

You must be logged in to vote
0 replies
Comment options

Hi, hope everyone is doing well. Since March things have moved on and python 3.7 has ended security updates last month. Raising a couple of points for discussion:

  • Are there any thoughts on a timeline for the release of the 1.2 and beyond versions?
  • Will any (security) issues raised before that be considered in a patch release until that time?

Many thanks and keep up the good work!

You must be logged in to vote
0 replies
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Category
Polls
Labels
None yet
4 participants
@ambv@gsnedders@mbron@satch421

[8]ページ先頭

©2009-2025 Movatter.jp