-
Notifications
You must be signed in to change notification settings - Fork 39
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
[securedrop-proxy] bookworm CI is failing because of pyyaml incompatibility with cython 3 #1681
Comments
The issue is tracked at: yaml/pyyaml#601 (and yaml/pyyaml#724 for 5.x). Instead of (option
You could also apply a different hack that lets pyyaml work with Cython 3+ such as:
The first seems work by finding the stuff Cython 3+ decided to hide better (in cython/cython#4498) but this might break later (as presumably Cython is hiding this better as it intends to jettison this at some point; likely during the upcoming Currently pyyaml has opted to not merge any of the above, instead opting to pin Cython < 3 for the yaml/pyyaml#702 applied workaround in pyyaml 6.0.1+ and the yaml/pyyaml#736 instructions which essentially has one do this same workaround oneself for pyyaml < 6.0.1. |
Thanks @Uzume! We already do build our own cython + pyyaml wheels for production installs (see https://github.com/freedomofpress/securedrop-builder/tree/main/securedrop-proxy/wheels) so this is just about unbreaking CI, which I'd like to avoid too many temporary hacks for... The one piece of context that's relevant here is that in production deployments we're still on bullseye, so it's ok if bookworm CI is failing for a while whether because we're waiting on upstream or just dropping the dependency. |
@legoktm: pyyaml will soon be forced to make some major changes anyway. Later this year |
Oooh, gotcha. Honestly then it seems like #1684 (removing pyyaml) is the only thing really worth spending time on. |
These are failing because of <#1681>. Our plan is to just replace them entirely with proxy v2, so just skip these jobs for now so commits can at least get a green check again.
These are failing because of <#1681>. Our plan is to just replace them entirely with proxy v2, so just skip these jobs for now so commits can at least get a green check again.
These are failing because of <#1681>. Our plan is to just replace them entirely with proxy v2, so just skip these jobs for now so commits can at least get a green check again.
There are no Python 3.11 wheels for pyyaml 5.4.1 so we've been building it from source in CI, but that's now broken with the release of Cython 3. There's a good amount of discussion in yaml/pyyaml#736 and yaml/pyyaml#728.
Our options forwards are:
cython<3
The text was updated successfully, but these errors were encountered: