You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Originally posted by ElliottKasoar November 15, 2024
As we increase the number of dependencies, I'm increasingly questioning the suitability of poetry for our dependency management.
In particular, the performance for resolving dependencies is becoming quite slow e.g. 1-5 minutes, and we're limited by the flexibility of optional dependencies, as I believe that poetry requires consistency between all extras, even if they're not installed, which may prevent us supporting/upgrading further MLIPs.
It's also worth noting that poetry 2.0 is on its way, with full PEP 621 support, which may include other improvements, but also means we may need to restructure pyproject.toml anyway.
In terms of improving efficiency, uv seems like a promising potential alternative, but I'm not sure whether it is sufficiently flexible or mature.
Any other suggestions are welcome.
The text was updated successfully, but these errors were encountered:
Discussed in #351
Originally posted by ElliottKasoar November 15, 2024
As we increase the number of dependencies, I'm increasingly questioning the suitability of poetry for our dependency management.
In particular, the performance for resolving dependencies is becoming quite slow e.g. 1-5 minutes, and we're limited by the flexibility of optional dependencies, as I believe that poetry requires consistency between all extras, even if they're not installed, which may prevent us supporting/upgrading further MLIPs.
It's also worth noting that poetry 2.0 is on its way, with full PEP 621 support, which may include other improvements, but also means we may need to restructure pyproject.toml anyway.
In terms of improving efficiency, uv seems like a promising potential alternative, but I'm not sure whether it is sufficiently flexible or mature.
Any other suggestions are welcome.
The text was updated successfully, but these errors were encountered: