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

Add option to use existing Python installation #84

Closed
psalz opened this issue Oct 30, 2024 · 1 comment · Fixed by #85
Closed

Add option to use existing Python installation #84

psalz opened this issue Oct 30, 2024 · 1 comment · Fixed by #85

Comments

@psalz
Copy link
Contributor

psalz commented Oct 30, 2024

Due to this unresolved issue with the setup-python action I'm currently unable to use this action on our self-hosted runners. Since we already have Python 3.12 pre-installed on the runners however, it would be great if there was an option to skip the installation step and simply use the existing installation instead!

Edit: Or maybe even better a python-path option, that if set, skips the setup-python action and uses it to create the venv (i.e. something like "${{ steps.setup-python.outputs.python-path || inputs.python_path }}" -m venv "${GITHUB_ACTION_PATH}/venv")

@platisd
Copy link
Owner

platisd commented Oct 30, 2024

I can take a look but don't have a good way of testing it. Sounds like you have a good solution to the issue though?
Feel free to provide a PR that addresses this in the meanwhile.

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 a pull request may close this issue.

2 participants