-
Notifications
You must be signed in to change notification settings - Fork 417
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
PIPX_DEFAULT_PYTHON not as flexible as --python
#1523
Comments
Personally I don’t think it is a good idea to set |
Just pass the executable name or path, i.e. Try Although
It looks like "python launcher", package
https://github.com/pytest-dev/py Just pass the executable name or path. |
@mcint Did you generate your response using ChatGPT? It does not seem to make sense at all. |
I'm all ears if you want to meaningfully invite me to engage. Sorry that adding context from my own brief poking around has proved inscrutably beneath engagement. Am I mistaken in assuming "python launcher" that handles finding a python version when passed a version number is https://pypi.org/project/py/? It seems that your request [support version-number-only specification] [additionally, when passed as an environment variable], is provided by a legacy library. I would love to be corrected, and learn about better tools or other tools for managing python environment in succinct and easy ways. |
In case someone is reading this who is not a generative IA, answer to the question posted above:
Yes, you are. The Python launcher for Windows ( |
Describe the bug
While
--python
allows flexible ways of specifying the desired interpreter (by version, by path...), the environment variablePIPX_DEFAULT_PYTHON
only allows a full path to the Python executable.How to reproduce
Expected behavior
The text was updated successfully, but these errors were encountered: