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

Follow SPEC-0 for minimum supported versions of dependencies #1177

Closed
2 of 3 tasks
ivirshup opened this issue Jun 3, 2024 · 0 comments · Fixed by #1189
Closed
2 of 3 tasks

Follow SPEC-0 for minimum supported versions of dependencies #1177

ivirshup opened this issue Jun 3, 2024 · 0 comments · Fixed by #1189
Labels
python api Related to the API tech

Comments

@ivirshup
Copy link
Collaborator

ivirshup commented Jun 3, 2024

Motivation

https://scientific-python.org/specs/spec-0000/

It would be nice to have a clear policy on what the support window for dependencies are. This makes it clear when we can use newer features, and when we can stop supporting old versions of libraries.

As an illustration of why this is important, let's say a user comes across a bug specific to python 3.8. It could turnout that this is a bug in all the versions of pandas that support 3.8, but was fixed after pandas dropped support for 3.8. Now it's basically on us to solve bugs in dependencies since we have a larger support window that our dependencies do.

Definition of Done

Bump minimum versions of dependencies and change policies around this going forward.

Tasks

  • Make sure no important downstream tasks are depending on an old version of a dep (there may be some tiledb thing around python 3.8?)
  • Bump the minimum versions
  • Remove CI/ CD infra that is specific to old versions
@ivirshup ivirshup added the tech label Jun 3, 2024
@pablo-gar pablo-gar added the python api Related to the API label Jun 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
python api Related to the API tech
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants