Closed stefanpantic-pdftools closed 1 year ago
Same for me with other libraries.
PR's are welcome. I don't fully grasp the issue to make a proper PR, can someone elaborate? what happens if we lock cython? what happens if you install cython<3.x in your project?
@woile We are experiencing same issue and run the action from a GHES runner. This was working as of 3 days ago and we use Commitizen action to create all our releases. Was there a recent change to the upstream dependency @stefanpantic-pdftools ?
`gpg (GnuPG) 2.4.3 libgcrypt 1.10.2 Copyright (C) 2023 g10 Code GmbH License GNU GPL-3.0-or-later https://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law.
Home: /github/home/.gnupg Supported algorithms: Pubkey: RSA, ELG, DSA, ECDH, ECDSA, EDDSA Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH, CAMELLIA128, CAMELLIA192, CAMELLIA256 Hash: SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224 Compression: Uncompressed, ZIP, ZLIB, BZIP2 git version 2.40.1 Configuring Git username, email, and pull behavior... Git name: github-actions[bot] Git email: github-actions[bot]@users.noreply.github.com pip install commitizen WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag. Collecting commitizen Downloading commitizen-3.5.3-py3-none-any.whl (57 kB) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 57.1/57.1 kB 13.4 MB/s eta 0:00:00 Collecting importlib_metadata<7,>=4.13 Downloading importlib_metadata-6.8.0-py3-none-any.whl (22 kB) Collecting termcolor<3,>=1.1 Downloading termcolor-2.3.0-py3-none-any.whl (6.9 kB) Collecting decli<0.7.0,>=0.6.0 Downloading decli-0.6.1-py3-none-any.whl (7.8 kB) Collecting pyyaml>=3.08 Downloading PyYAML-6.0.tar.gz (124 kB) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 125.0/125.0 kB 72.8 MB/s eta 0:00:00 Installing build dependencies: started Installing build dependencies: finished with status 'done' Getting requirements to build wheel: started Getting requirements to build wheel: finished with status 'error' error: subprocess-exited-with-error
× Getting requirements to build wheel did not run successfully.
│ exit code: 1
╰─> [48 lines of output]
running egg_info
writing lib/PyYAML.egg-info/PKG-INFO
writing dependency_links to lib/PyYAML.egg-info/dependency_links.txt
writing top-level names to lib/PyYAML.egg-info/top_level.txt
Traceback (most recent call last):
File "/usr/local/lib/python3.8/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 353, in
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.
Notice: A new release of pip is available: 23.0.1 -> 23.2 Notice: To update, run: pip install --upgrade pip`
The original issues has been fixed, is it the case for commitizen as well? Can the reporters check if it works now? Thanks
@woile fixed with https://github.com/yaml/pyyaml/pull/702#issuecomment-1639058497, closing now.
Quick update, nothing changed on commitizen, before or after.
Pyyaml v5 and v6 are using a very lose version of cython, and cython v3 introduced a breaking change in pyyaml, thus breaking commitizen.
pyyaml released v6.0.1
pinning cython to <3
, but v5
is still broken. If you cannot upgrade pyyaml, a solution is to pin cython
in your repo.
[tool.poetry.dependencies]
Cpython = "<3.0.0"
For commitizen case, if you still see this issue:
poetry update
so the lock is updated to use v6.0.1
v5
, so pin cython
pip install "Cython<3.0" pyyaml
The github action should not be affected anymore.
Please be mindful with the maintainers, everyone is aware of this issues and they are trying to fix it asap. I think pyyaml will introduce a v5
fix soon as well.
Description
This issue is preventing me from installing Commitizen: https://github.com/yaml/pyyaml/issues/601
Can Commitizen lock the Cython version to something pre 3.0.0?
Steps to reproduce
Current behavior
Desired behavior
I can install Commitizen.
Screenshots
No response
Environment