lxml

No PyPI wheel for 4.9.3-cp38-cp38-macosx

Bug #2035206 reported by Paul Natsuo Kishimoto
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
lxml
Confirmed
Medium
Unassigned

Bug Description

Hi,

For lxml-4.9.3, the following wheels are on PyPI:
- lxml-4.9.3-cp36-cp36m-macosx_11_0_x86_64.whl
- lxml-4.9.3-cp39-cp39-macosx_11_0_x86_64.whl
- lxml-4.9.3-cp310-cp310-macosx_11_0_x86_64.whl
- etc.

For lxml-4.9.2, there are:
- lxml-4.9.2-cp36-cp36m-macosx_10_15_x86_64.whl
- lxml-4.9.2-cp37-cp37m-macosx_10_15_x86_64.whl
- lxml-4.9.2-cp38-cp38-macosx_10_15_x86_64.whl
- lxml-4.9.2-cp39-cp39-macosx_10_15_x86_64.whl
- etc.

Specifically, for 4.9.3 wheels for cp37 and cp38 appear to be missing. I noticed this when a change to a CI workflow caused it to look for the latter; it fell back to trying to build from source.

I have looked in the documentation and other issues to see if this is intentional or if pre-built wheels for these versions are specifically excluded/not supported, but could not find any direct information. It's fine if that is the case (and will be for future versions?), I would just appreciate confirmation if so.

Revision history for this message
scoder (scoder) wrote :

Yes, there is a build failure on these versions, e.g.
https://github.com/lxml/lxml/actions/runs/6256930321

This is due to changes in CPython in those versions that were only fixed in Python 3.9. I'm not sure how to work around them. Basically, the MACOSX_DEPLOYMENT_TARGET needs to match that of the CPython version where it's being built, which on GitHub Actions is currently 11.7.

I could set MACOSX_DEPLOYMENT_TARGET=11.7 for the Python 3.7/8 wheels, and that might then make it work again – as long as the Python installations in CI are not updated. But I'm not sure if a dependency on macOS 11.7 would make users of these old Python versions overall happy.

Changed in lxml:
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
Paul Natsuo Kishimoto (khaeru) wrote :

Okay, thanks for letting us know! I definitely have felt the pain of wrestling with dependencies on GHA runners…

For the moment we pin to "lxml != 4.9.3" in our workflows and that serves as a workaround. I'll monitor the notifications here in case you find a way to resolve it, but again no urgency.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.