Skip to content

Use uv to manage python deps #95

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

Merged
merged 1 commit into from
Mar 19, 2025
Merged

Use uv to manage python deps #95

merged 1 commit into from
Mar 19, 2025

Conversation

rauhul
Copy link
Member

@rauhul rauhul commented Mar 19, 2025

Instead of having users manually manage python venvs this commit migrates the python scripts to use uv which can handle installing script dependencies automatically. Additionally it doesn't require sourcing a venv setup script in every shell where you want to build.

A further improvement on the swift swift side should also be made to use swiftly to manage swift toolchain versions instead of the TOOLCHAINS env variable.

@rauhul rauhul requested a review from kubamracek as a code owner March 19, 2025 18:37
Instead of having users manually manage python venvs this commit
migrates the python scripts to use `uv` which can handle installing
script dependencies automatically. Additionally it doesn't require
sourcing a venv setup script in every shell where you want to build.

A further improvement on the swift swift side should also be made to use
swiftly to manage swift toolchain versions instead of the `TOOLCHAINS`
env variable.
@rauhul rauhul merged commit 8887cc9 into main Mar 19, 2025
20 checks passed
@rauhul rauhul deleted the uv branch March 19, 2025 18:49
rauhul added a commit that referenced this pull request May 3, 2025
Instead of having users manually manage python venvs this commit
migrates the python scripts to use `uv` which can handle installing
script dependencies automatically. Additionally it doesn't require
sourcing a venv setup script in every shell where you want to build.

A further improvement on the swift swift side should also be made to use
swiftly to manage swift toolchain versions instead of the `TOOLCHAINS`
env variable.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant