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

Decide on range of supported version for the core dependencies, and test them in CI #157

Open
Luthaf opened this issue Mar 18, 2024 · 0 comments
Labels
Discussion Issues to be discussed by the contributors Infrastructure: Miscellaneous General infrastructure issues Priority: Low Non-urgent issues to handle last.

Comments

@Luthaf
Copy link
Member

Luthaf commented Mar 18, 2024

This was prompted by torch dependencies, but should apply to all of the dependencies of the main code. For all of them, we should decide on the range of supported version, and test with both the lowest and highest supported version on CI.

From the current set of dependencies:

  • ase: I guess we only support the latest version?
  • torch: we should support more than the latest release, especially for people running on older clusters. metatensor-torch supports up to 1.11, we could do something more recent here (1.13 or even 2.0).
  • hydra-core: we'll need some kind of check once Drop hydra? #149 is resolved
  • metatensor-xxx: we are pinning these, I think we can continue this way for a while.
@PicoCentauri PicoCentauri added Discussion Issues to be discussed by the contributors Priority: Low Non-urgent issues to handle last. Infrastructure: Miscellaneous General infrastructure issues and removed infrastructure labels Jun 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Discussion Issues to be discussed by the contributors Infrastructure: Miscellaneous General infrastructure issues Priority: Low Non-urgent issues to handle last.
Projects
None yet
Development

No branches or pull requests

2 participants