Skip to content
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

Support .python-version files as input to with python-version #211

Open
JacobHayes opened this issue Dec 24, 2024 · 0 comments
Open

Support .python-version files as input to with python-version #211

JacobHayes opened this issue Dec 24, 2024 · 0 comments

Comments

@JacobHayes
Copy link

In simple projects, I use a .python-version file to set the version and don't use GHA matrix builds across python versions (ie: no python version ref in workflow file).

I would like to use setup-uv's python installation and particularly the automatic venv activation, but don't want to duplicate the python version in both the .python-version file _and_ the GHA workflow. Right now, I just use setup-uvand then runuv sync --frozenin the next step (which will implicitly install from.python-version`), which works fine but doesn't handle the venv activation for subsequent steps.

The presence of a .python-version file probably shouldn't automatically trigger the python install / venv activation, but perhaps the python-version flag could be extended to support a reference to the file?

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

No branches or pull requests

1 participant