-
Notifications
You must be signed in to change notification settings - Fork 519
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
Error installing Pyyaml==5.4, Cython_sources #724
Comments
I just had the same issue with pyyaml 6.0.0 Duplicate of #723? |
Both are duplicates of #601. This has been on the horizon for a long time apparently. |
Yes, but I see it is again backup discussion, just 50 minutes ago ! |
Yea seems like now things are going to break more loudly for others since Cython3 was released. |
You can use PyYaml 5.3.1 until the issue is resolved. |
This has broken Python 3.12 as well; there aren't pre-built wheels for 3.12 yet (ABI is now supposed to be stable as of beta 4, so you can add them ;) ) Setting:
Does work for now on 3.12. |
@AlexDld Thank you! Worked for me! |
Affecting us too and our security policy won't let us downgrade to 5.3 because of pre-5.4 vulnerabilities But |
We are experiencing the same issue today with On Friday: Today: |
Cython 3.0 came out since Friday. |
Cython 3 was released 4 hours ago: https://pypi.org/project/Cython/3.0.0/#history This coincides with when our PyYAML 6.0.0 installs via Poetry in Alpine Linux containers started failing. 😢 |
We cannot use PyYAML 5.3 due to dependencies requiring 5.4. Is there a way to have PyYAML use Cython<3 for its installation? |
Thank you! Adding |
Downgrade pyyaml - yaml/pyyaml#724 Fix YAML::PP - path to event processor changed Remove raku Build problems: ===SORRY!=== Could not find YAMLish at line 3 in: inst#/raku inst#/root/.perl6 inst#/rakudo/share/perl6/site inst#/rakudo/share/perl6/vendor inst#/rakudo/share/perl6/core ap# nqp# perl5# Remove Java - build problems... Upgrade containers
Downgrade pyyaml - yaml/pyyaml#724 Fix YAML::PP - path to event processor changed Remove raku Build problems: ===SORRY!=== Could not find YAMLish at line 3 in: inst#/raku inst#/root/.perl6 inst#/rakudo/share/perl6/site inst#/rakudo/share/perl6/vendor inst#/rakudo/share/perl6/core ap# nqp# perl5# Remove Java - build problems... Upgrade containers
Downgrade pyyaml - yaml/pyyaml#724 Fix YAML::PP - path to event processor changed Remove raku Build problems: ===SORRY!=== Could not find YAMLish at line 3 in: inst#/raku inst#/root/.perl6 inst#/rakudo/share/perl6/site inst#/rakudo/share/perl6/vendor inst#/rakudo/share/perl6/core ap# nqp# perl5# Remove Java - build problems... Upgrade containers Fix duplicate runtime
doesn't work for me |
See yaml/pyyaml#724 for details
…ctivity Juniper#43 added ARM64 support. By some reason PyYAML 5.4 could not be built on ARM64 based ubuntu. Probably this issue: yaml/pyyaml#724.
I wanted to install csv2ofx on python311 and ran into this error.
and
solved it for me |
See yaml/pyyaml#724 for details. PyYAML 6.0.2 does not work because some dependencies depend on PyYAML 5.
see yaml/pyyaml#724 for the origin of the error. We can remove this once pyyaml 7.0 is released.
I am tyring to install the 5.4 version, but I got the following output:
`Collecting pyyaml==5.4
Using cached PyYAML-5.4.tar.gz (174 kB)
Installing build dependencies ... done
Getting requirements to build wheel ... error
error: subprocess-exited-with-error
× Getting requirements to build wheel did not run successfully.
│ exit code: 1
╰─> [68 lines of output]
/private/var/folders/jq/gc3kdhbj0tg3r798nj8wlgl86xxhf9/T/pip-build-env-qbudtvrl/overlay/lib/python3.11/site-packages/setuptools/config/setupcfg.py:293: _DeprecatedConfig: Deprecated config in
setup.cfg
!!
note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error
× Getting requirements to build wheel did not run successfully.
│ exit code: 1
╰─> See above for output.
note: This error originates from a subprocess, and is likely not a problem with pip.`
The text was updated successfully, but these errors were encountered: