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

In pyproject.toml, define each requirement using range of versions #404

Open
thomass-dev opened this issue Sep 27, 2024 · 3 comments · May be fixed by #490
Open

In pyproject.toml, define each requirement using range of versions #404

thomass-dev opened this issue Sep 27, 2024 · 3 comments · May be fixed by #490
Assignees
Labels
chore Internal enhancement work to be done

Comments

@thomass-dev
Copy link
Collaborator

thomass-dev commented Sep 27, 2024

Actually, user can install skore without restrictions on the skore's dependencies.
It means that user can use old (and incompatible) version of one of dependencies.
With an incompatible dependency version, some errors can occur obscurely to the user only at the runtime.

We can't be compatible with all of versions of all package.
The convention is to define a range of version between two majors release.

@augustebaum
Copy link
Contributor

Would it be acceptable to perform a pip freeze on my machine and use the versions I have as lower bounds?

@thomass-dev
Copy link
Collaborator Author

I don't know if its enough.
We don't want to be restrictive, so we need to test the lowest versions we can accept on each dependencies.

@augustebaum augustebaum self-assigned this Oct 14, 2024
@tuscland tuscland assigned thomass-dev and unassigned augustebaum Oct 18, 2024
@tuscland
Copy link
Member

Assigned to @thomass-dev so he can bring the issue forward.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chore Internal enhancement work to be done
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants