-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Build failure with pyyaml 6.0 and PEP517 #8287
Comments
Check if you have 6.0.1 in the lock file. 6.0 was broken by Cython 3.0 release, they patched it in 6.0.1 |
I also ran into this issue, but I'm currently locked to PyYAML 5.4.1. There's a workaround described in yaml/pyyaml#736 and it does work.... I'm hoping it's possible (I missed it in the docs?) to get poetry to express an equivalent of the PyYAML = {version = '5.4.1', build_constraints = ['Cython < 3.0']}
# or some key in a section other than [tool.poetry.dependencies]? That way I'm not left just hoping that my teammates will notice that the README now says to use this obscure env var with the |
No, we don't handle build dependencies overriding, as this is considered a job for the project to express those. Also, the solution you linked won't work in modern versions of Poetry, since we don't use If you need a workaround for older |
At risk of displaying an embarrassing lack of knowledge, isn't poetry (or pipenv or whatever) the way for a project to express its dependencies? If I can't capture this comprehensively in poetry, I must use something to fill in the gaps like a script, Make, etc. I'm not opposed to that, really, but I feel I've at least partially misunderstood either the aim of poetry or the distinction between a dependency and a "build dependency override." |
Yeah upgrading to |
We experienced a build failure on GitHub Actions exactly the same as python-poetry/poetry#8287 See also: yaml/pyyaml#601
Amazingly enough, it was working fine for me before. When I switched computers and git cloned and then poetry installed, I had this problem. I solved the problem by deleting the lock file. |
This worked arround the problem in a python 3.12 poetry install (my other dependencies wanted pyyaml = { version = "!=6.0.0,!=5.4.0,!=5.4.1" } |
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. |
-vvv
option) and have included the output below.Issue
I'm experiencing a build failure when trying to install pyyaml 6.0 using Poetry on my CD system (Github Actions).
The log shows that pyyaml 6.0 does not support PEP 517 builds; however, I've confirmed that it does by running pip wheel --use-pep517 "pyyaml (==6.0)", which worked with no errors.
Logs full logs:
The text was updated successfully, but these errors were encountered: