-
Notifications
You must be signed in to change notification settings - Fork 661
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
[BUG] Cython 3.0.0 release breaking flytekit editable install setup #3874
Comments
@Benjamintdk , thanks for opening the issue! I'm following up on it on flyteorg/flytekit#1752. |
@Benjamintdk , can you confirm which combination of python version and architecture you're seeing this? |
Hi @eapolinario, am currently using Python 3.11.3 and MacOS. |
Can you rebase? If this is for local development only, then flyteorg/flytekit#1746 should give you enough room to start developing locally. |
I managed to get around this temporarily by downgrading pyyaml to 5.3.1 instead, but this has security vulnerabilities, so will definitely look for other alternatives moving forward. Would be happy to have a discussion and work on a more permanent fix for this. |
Closing this as we have a workaround in place. It's a bit unfortunate that for older versions of python we end up installing a version of pyyaml that's affected by a serious CVE, but unless that project decides to handle it there isn't a lot that flytekit can do about it. |
Describe the bug
Getting a
cythonsources
error when I follow this set of instructions to set up my environment and runmake setup
.It seems that the recent version of Cython 3.0.0 that was released just yesterday was causing pyyaml 5.4.2 to break. It also seems that pyyaml's version has been constrained to under 6 to accommodate for docker compose, as per this issue.
Expected behavior
Running
make setup
should not throw an error and the installation should complete successfully.Additional context to reproduce
No response
Screenshots
No response
Are you sure this issue hasn't been raised already?
Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: