You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched the issues of this repo and believe that this is not a duplicate.
If an exception occurs when executing a command, I executed it again in debug mode (-vvv option).
OS version and name: python:3.10-alpine docker container
Poetry version: 1.1.13 and 1.2.0a2
Link of a Gist with the contents of your pyproject.toml file: n/a
Issue
Poetry isn't finding musllinux binary wheel for the cryptography package that pip finds. Instead, it compiles from source on Alpine. Pip finds the binary package and installs cryptography successfully.
This gist contains scripts to reproduce the issue.
Reacted by Matt Carr, Ashley Sommer, George Marshall, erin and Allan Chain
I've got the same problem, with the orjson package.
orjson now (since v3.6.7) publishes a musllinux binary wheel compatible with Apline Linux.
Installing with pip3 install "orjson>=3.6.7" works fine (pip downloads and installs the musllinux bdist wheel), but installing with Poetry instead ignores the bdist and tries to build the package from source.
I'm having the same issue with the grpcio package - there are musl wheels available that pip finds but poetry doesn't - adds about 30 minutes to CI runs
In theory, the implementation of PEP 656 in packaging and Poetry's update of the package in #4749 should have fixed the issue. However, this issue can still persist due to poetry-core's vendored packaging version being older than what poetry uses. The changes in python-poetry/poetry-core#336 should fix this issue.
You can test this using the following snippet.
podman run --rm -i --entrypoint sh docker.io/python:3.10-alpine <<EOFset -xeapk add gcc libc-dev make libffi-dev curl gitpython -m pip install -q git+https://github.com/python-poetry/poetry.git@masterpython -m pip install -q git+https://github.com/python-poetry/poetry-core.git@masterpoetry new foobarcd foobarpoetry add cryptographyEOF
However, we seem to have a broader issue of Poetry re-using core's vendored packages and thereby being tied to the version there cusing some unexpected issues. While outside the scope of this particular issue, we should handle it in another issue.
Activity
ashleysommer commentedon Mar 22, 2022
I've got the same problem, with the orjson package.
orjson now (since v3.6.7) publishes a musllinux binary wheel compatible with Apline Linux.
Installing with
pip3 install "orjson>=3.6.7"works fine (pip downloads and installs the musllinux bdist wheel), but installing with Poetry instead ignores the bdist and tries to build the package from source.insertjokehere commentedon Apr 18, 2022
I'm having the same issue with the
grpciopackage - there are musl wheels available thatpipfinds but poetry doesn't - adds about 30 minutes to CI runsabn commentedon May 17, 2022
In theory, the implementation of PEP 656 in
packagingand Poetry's update of the package in #4749 should have fixed the issue. However, this issue can still persist due topoetry-core's vendoredpackagingversion being older than what poetry uses. The changes in python-poetry/poetry-core#336 should fix this issue.You can test this using the following snippet.
However, we seem to have a broader issue of Poetry re-using core's vendored packages and thereby being tied to the version there cusing some unexpected issues. While outside the scope of this particular issue, we should handle it in another issue.
sherbang commentedon Aug 18, 2022
Closed as it's working for me in poetry 1.2.0b1 and later
github-actions commentedon Mar 1, 2024
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.