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.

Sign up for GitHub

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

Jump to bottom

Dependency Versioning Stategy #1368

Open
npatki opened this issue Apr 10, 2023 · 0 comments
Open

Dependency Versioning Stategy #1368

npatki opened this issue Apr 10, 2023 · 0 comments
Labels
maintenance Tasks related to infrastructure & dependencies

Comments

@npatki
Copy link
Contributor

npatki commented Apr 10, 2023

Problem Description

Currently, all libraries in the SDV ecosystem have narrow and fixed dependency ranges (with a min and max).

Sometimes as external libraries change, users may have problems installing the SDV such as #1349, #1360, #1345.

Expected behavior

I'm filing this as a broad issue to think about the SDV dependency versioning strategy. In addition to supporting the latest version of pandas (#1366) and pytorch (#1365), we should also think about how to enable the broadest set of of acceptable versions.
@npatki npatki added the maintenance Tasks related to infrastructure & dependencies label Apr 10, 2023
This was referenced Apr 10, 2023
Closed
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
maintenance Tasks related to infrastructure & dependencies
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@npatki