Conversation
Simrayz
added
dependencies
Test results 6 files 888 suites 1m 54s ⏱️ Results for commit 5354f74. ♻️ This comment has been updated with latest results. |
Simrayz
added
the
nonews
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1788 +/- ##
=======================================
Coverage 82.57% 82.57%
=======================================
Files 137 137
Lines 6552 6552
=======================================
Hits 5410 5410
Misses 1142 1142 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Simrayz
force-pushed
the
chore/use-uv-for-environment-management
branch
from
a4172e5 to
66a9689
Compare
Simrayz
removed
the
nonews
Simrayz
force-pushed
the
chore/use-uv-for-environment-management
branch
from
66a9689 to
421d983
Compare
Simrayz
force-pushed
the
chore/use-uv-for-environment-management
branch
from
421d983 to
5354f74
Compare
|
| --------------------- | ||
|
|
||
| To generate a secret key to be used in the `cmd.sh` file one can use | ||
| To generate a secret key to be used in the `.env` file one can use |
There was a problem hiding this comment.
How would I run with multiple sets of environment variables?
I don't use .env today, because I regularly use two different sets of environment variables, and frequently three when testing something.
There was a problem hiding this comment.
Fair point :) My reasoning was to try to avoid creating custom "cmd.sh" script files instead of using the uv tooling. I can look into how we can support switching between different environments.
| dev = [ | ||
| "django-debug-toolbar", | ||
| "coverage", | ||
| "django-extensions", | ||
| "ruff", | ||
| "djlint", | ||
| "ipython", | ||
| "pre-commit", | ||
| "pydotplus", | ||
| "python-dotenv", | ||
| "towncrier", | ||
| "unittest-xml-reporting", | ||
| "werkzeug", | ||
| "tox>=4", | ||
| "build", # for debugging builds/installs |
There was a problem hiding this comment.
It will probably be possible to switch to dependency groups instead, at least for dev.
| We recommend using virtualenv or virtualenvwrapper to create | ||
| a place to stash Argus' dependencies. |
There was a problem hiding this comment.
I will still need to be able to use virtualenvwrapper because I need to switch between different sets of dependencies...
| uv pip compile --no-strip-extras --output-file requirements-django52.txt {posargs} pyproject.toml requirements/django52.txt constraints.txt | ||
| uv pip compile --no-strip-extras --output-file requirements-django60.txt {posargs} pyproject.toml requirements/django60.txt constraints.txt |
There was a problem hiding this comment.
Phew! Multiple lock-files are important, oh yes.
| The repo has a ``Makefile`` to help with development. The rules depend on having | ||
| ``uv`` installed. |
There was a problem hiding this comment.
| The repo has a ``Makefile`` to help with development. The rules depend on having | |
| ``uv`` installed. | |
| The repo has a ``Makefile`` to help with development. Some of the rules depend on having | |
| ``uv`` installed. |
2 participants
Scope and purpose
Fixes #1787.
Replaces pip, pip-tools, and venv with uv across CI, Docker, tox, and local dev setup.
This pull request
Contributor Checklist