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

[BUG] typing_extensions needs a pin for >= 4.0.0 for pip packages #13616

Closed
jarmak-nv opened this issue Jun 26, 2023 · 0 comments · Fixed by #13618
Closed

[BUG] typing_extensions needs a pin for >= 4.0.0 for pip packages #13616

jarmak-nv opened this issue Jun 26, 2023 · 0 comments · Fixed by #13618
Assignees
Labels
bug Something isn't working

Comments

@jarmak-nv
Copy link
Contributor

Describe the bug
The Databricks runtime environments have a bunch of preinstalled pip packages including a pretty old version (3.10.x) of the typing-extensions package that predates the addition of Self (4.0.0+).

It appears that the cudf pip package doesn't constrain the version typing_extensions. A constraint of say >= 4.0.0 should be added.

Steps/Code to reproduce bug

  • Start a databricks runtime environment
  • Install cuDF through pip
  • Attempt to use cuDF

Expected behavior
cuDF can be used within Databricks through pip.

Environment overview (please complete the following information)

  • Environment location: Databricks
  • Method of cuDF install: pip

Environment details
N/A

Additional context
N/A

@jarmak-nv jarmak-nv added Needs Triage Need team to review and classify bug Something isn't working labels Jun 26, 2023
@shwina shwina self-assigned this Jun 26, 2023
@shwina shwina added python and removed Needs Triage Need team to review and classify labels Jun 26, 2023
@github-project-automation github-project-automation bot moved this from In Progress to Done in cuDF/Dask/Numba/UCX Jun 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants