Skip to content
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

AttributeError: cython_sources when installing KFP SDK + running Python components #9745

Closed
connor-mccarthy opened this issue Jul 18, 2023 · 3 comments
Assignees
Labels
area/sdk kind/bug lifecycle/stale The issue / pull request is stale, any activities remove this label.

Comments

@connor-mccarthy
Copy link
Member

TLDR: Cython 3.0.0 just GA'd and introduced a regression which affects building pyyaml on some operating systems with some versions of Python. Upgrade to the latest version of the KFP SDK (v1 or v2) and recompile your components to get the fix.

Short term fix options

  • Upgrade to the latest version of the KFP SDK within the major version you are using (1.8.22 and 2.0.1 at the time of writing this)
  • Switch to a Python image/version that does not exhibit this error (python:3.7 appears to work in some cases)

With either option, recompile your components to get the fix.

Useful information

Reproducing

  • docker run python:3.7 pip install 'kfp==1.8.20' PASS

  • docker run python:3.10 pip install 'kfp==1.8.20' FAIL

  • docker run python:3.10 pip install 'kfp==1.8.22' PASS

  • docker run python:3.10 pip install 'kfp>=2.0.0,<3.0.0' PASS

Long term fix

We are nearing completion a change that extracts a KFP runtime package, preventing similar failures for existing components that use prior versions of the KFP SDK (versions we cannot patch once released).

@atemate
Copy link

atemate commented Jul 24, 2023

Seeing this issue on GCP Vertex that uses Kubeflow internally. Forcing pyyaml==5.3.1 with non-working kfp==1.8.21 fixes the issue (following already mentioned comment)

@github-actions
Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the lifecycle/stale The issue / pull request is stale, any activities remove this label. label Oct 23, 2023
Copy link

This issue has been automatically closed because it has not had recent activity. Please comment "/reopen" to reopen it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/sdk kind/bug lifecycle/stale The issue / pull request is stale, any activities remove this label.
Projects
Status: Closed
Development

No branches or pull requests

2 participants