Use setup.py to install dependencies in docker#434
Merged
karlicoss merged 4 commits intokarlicoss:masterfrom Jun 24, 2025
Merged
Use setup.py to install dependencies in docker#434karlicoss merged 4 commits intokarlicoss:masterfrom
karlicoss merged 4 commits intokarlicoss:masterfrom
Conversation
karlicoss
reviewed
Jan 10, 2024
Owner
|
Thanks! Sorry just noticed -- somehow didn't receive the email notification |
wilt00
force-pushed
the
docker-setupdotpy
branch
from
9bb2aa9 to
5cd2d7d
Compare
Contributor
Author
|
Sorry for the drive-by PR @karlicoss ! I've finally fixed the CI issues here. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
While building from the Dockerfile, I ran into some issues caused by pip resolving sqlalchemy to v1 instead of v2. This PR changes the Dockerfile to install directly from setup.py, rather than indirectly from a list of dependencies, to hopefully prevent issues like this from coming up in the future.
It looks like the reason we originally went with the individual dependencies approach is because setuptools-scm needs to get the version from the git history. Since we don't want to bloat the container by copying the entire git history into it, setuptools-scm can't find the version and the installation fails. Since then, it looks like setuptools-scm has added an override environment variable which we can use to pass in a version explicitly during the build.