Bump lxml from 4.9.2 to 5.2.1
Bumps lxml from 4.9.2 to 5.2.1.
Changelog
Sourced from lxml's changelog.
5.2.1 (2024-04-02)
Bugs fixed
LP#2059910: The minimum CPU architecture for the Linux x86 binary wheels was set back to "core2", but with SSE 4.2 enabled.
LP#2059977:
Element.iterfind("//absolute_path")failed with aSyntaxErrorwhere it should have issued a warning.GH#416: The documentation build was using the non-standard
whichcommand. Patch by Michał Górny.5.2.0 (2024-03-30)
Other changes
LP#1958539: The
lxml.html.cleanimplementation suffered from several (only if used) security issues in the past and was now extracted into a separate library:https://github.com/fedora-python/lxml_html_clean
Projects that use lxml without "lxml.html.clean" will not notice any difference, except that they won't have potentially vulnerable code installed. The module is available as an "extra" setuptools dependency "lxml[html_clean]", so that Projects that need "lxml.html.clean" will need to switch their requirements from "lxml" to "lxml[html_clean]", or install the new library themselves.
The minimum CPU architecture for the Linux x86 binary wheels was upgraded to "sandybridge" (launched 2011), and glibc 2.28 / gcc 12 (manylinux_2_28) wheels were added.
Built with Cython 3.0.10.
5.1.2 (2024-??-??)
Bugs fixed
- LP#2059977:
Element.iterfind("//absolute_path")failed with aSyntaxErrorwhere it should have issued a warning.5.1.1 (2024-03-28)
... (truncated)
Commits
47f94ffUpdate changelog.932a41eUpdate macOS build isntructions.888153aMerge branch 'lxml-5.1'fcf00fbUpdate changelog.76fd4f9Fix SyntaxError in Element.iterfind() that should have been a warning.4faebe3Fix test.9b8e36dFix SyntaxError in Element.iterfind() that should have been a warning.175c66aBuild: Reduce the number of build jobs by disabling some old targets.06ad31cPrepare release of 5.2.1.24dafd3Build: Fix Makefile to work on systems withoutwhich(1)(GH-416)- Additional commits viewable in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)