-
-
Notifications
You must be signed in to change notification settings - Fork 349
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Switch to uv
in CI
#2956
Comments
Interesting, I'm totally on board with switching if the lockfiles are cross-platform. (I'm fine even if it doesn't though Oh, yeah unfortunately it doesn't do that yet:
|
But this project already uses the terrible pip-tools workflow. |
Yeah using this over Personally I'd rather |
Ignore me I found the discussion in #2790 |
Oh As for poetry it's mostly just my opinion (re: standardization and speed and poor past experience :'( ) |
Given the extensive discussion in #2790 - is |
As that blog entry describes, the ruff folks are also taking over Rye. At the rate Trio's reached consensus on a project package manager, it seems likely that this new option will be ready for prime time before we do. :P |
We use |
* Switch to use `uv`. Closes #2956 * Update ci.sh -U => --upgrade, for legibility * Revert changing wheel version to be lower * Make sure running without a venv works Also fix shellcheck reported issues * Try to fix getting python executable on windows * Make `PYTHON_PATH` work on both windows and linux * Add comment about python path variable * Detect if on Github CI and use system python if so * Try invoking with `python -m uv` * Install pinned uv version from the start Windows CI is failing because uv is trying to change it's own executable while running * Follow shellcheck suggestions * Use constraints instead of grep --------- Co-authored-by: John Litborn <11260241+jakkdl@users.noreply.github.com>
uv is a new tool from the Ruff guys that replaces
pip
andpip-tools
.This is mostly interesting because it's actually being benchmarked on Trio itself. Sounds like it's already been tested for us.
The text was updated successfully, but these errors were encountered: