pyproject.toml: avoid strong dependency with torch binary release #113
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Having a strong dependency with one specific binary release is problematical because: - it won't work on Linux a soon as the platform is not amd64, we support 4 architectures - if the dependency has a critical issue (e.g CVE), we need to also publish a release. Overall, we should relax all our dependencies.
|
We've a similar problem with |
|
Also, is there a reason why we don't pull psycopg3 like for ansible-ai-connect-service? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Having a strong dependency with one specific binary release is
problematical because:
4 architectures
publish a release.
Overall, we should relax all our dependencies.