-
Notifications
You must be signed in to change notification settings - Fork 725
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
use PyYAML 6.0.1 instead of 6.0 for recent ReFrame versions to fix problem with Cython 3.x #20879
use PyYAML 6.0.1 instead of 6.0 for recent ReFrame versions to fix problem with Cython 3.x #20879
Conversation
@boegelbot please test @ generoso |
@bedroge: Request for testing this PR well received on login1 PR test command '
Test results coming soon (I hope)... - notification for comment with ID 2182662114 processed Message to humans: this is just bookkeeping information for me, |
Test report by @boegelbot |
Test report by @bedroge |
@boegelbot please test @ jsc-zen3 |
@bedroge: Request for testing this PR well received on jsczen3l1.int.jsc-zen3.fz-juelich.de PR test command '
Test results coming soon (I hope)... - notification for comment with ID 2182687643 processed Message to humans: this is just bookkeeping information for me, |
Test report by @boegelbot |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Test report by @boegel |
Going in, thanks @bedroge! |
I ran into this when installing ReFrame on a system with Cython 3:
Apparently PyYAML 6.0 has a known issue regarding Cython 3, and is not compatible with this version:
yaml/pyyaml#736
They worked around it by pinning the Cython build constraint to < 3.0:
yaml/pyyaml#702
And they released 6.0.1 with (only) this workaround: https://github.com/yaml/pyyaml/blob/6.0.1/announcement.msg
This PR replaces 6.0 in the requirements.txt by 6.0.1 for recent ReFrame version. Since nothing else is changed in PyYAML, this should be a safe change.
ReFrame 4.4.x and newer already use 6.0.1, so this fix can be removed for those versions.