Repository navigation
feat: updating uv workspace and introducing pytest - #51
Merged
Merged
Conversation
# Conflicts: # codebuild/server/requirements-dev.txt # codebuild/server/requirements.txt # lambda/operations/requirements-dev.txt # lambda/startup/requirements-dev.txt
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
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.
what
moves the python setup off requirements files and onto a uv workspace, and fixes the release while i was in there.
deps
requirements*.txt-> onepyproject.tomlper package + oneuv.lockat the rootrequired-version).venvci
uv sync --locked, so a stale lock fails instead of driftingrelease
server.zipwas never built, so installs would 404 on it. one loop now builds all 3 python zipsprereleasecheckbox actually does something nowmisc
lambda-build/wasn't actually gitignored (inline comment broke the pattern)uventry instead of three pip onesafter pulling
direnv allow, then point your ide at.venv/bin/python