Migrates Package Management to UV pyproject Management#111
Closed
WeatherGod3218 wants to merge 4 commits into
Closed
Migrates Package Management to UV pyproject Management#111WeatherGod3218 wants to merge 4 commits into
WeatherGod3218 wants to merge 4 commits into
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
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
what the PR changes
This PR moves away from the manual installation of requirement.txt files and instead uses the UV package managers' syncing method
Why
why these changes were made
These changes were made to simplify dependency management, rather than having multiple separate requirements.txt files.
Another choice to do this migration was to encourage the use of modern tools, such as UV, rather than skipping over them. The updated documentation includes all the commands that somebody would need to get adjusted to UV, and aims to promote the use of newer and better technologies
Test Plan
how did you verify these changes did what you expected
The Dockerfile runs as expected, and the localhost web server functions properly
Env Vars
did you add, remove, or rename any environment variables
REMOVED SLACK_JUMPSTART_MESSAGE: This env var was redundant anyways, as the message was hardcoded into
config.py. This can be added back at a later date if wanted.Side Note: The Docker Compose file now uses an .env-file: rather than hardcoding each environment variable in an .env section.
Documentation
did you add or update any documentation. PRs should, at the minimum, update documentation when they make existing documentation out of date.
Documentation has been extensively updated in the
README.mdto help guide people on how to use UV for the project. It also includes the updated steps for developing locally.Checklist