Not possible to use multiple python versions for virtualenvs #685
Labels
Comments
wmellema
pushed a commit
to wmellema/puppet-python
that referenced
this issue
Feb 8, 2024
Issue voxpupuli#685 - Add: `python_path` variable to `python::pyvenv`
bastelfreak
added a commit
that referenced
this issue
Feb 8, 2024
* Add python_path to pyvenv class Issue #685 - Add: `python_path` variable to `python::pyvenv` * Fixed whitespace issue * Update manifests/pyvenv.pp Co-authored-by: Tim Meusel <tim@bastelfreak.de> * Updated reference.md --------- Co-authored-by: Wouter Mellema <w.mellema@iwink.nl> Co-authored-by: Tim Meusel <tim@bastelfreak.de>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, there seems to be no way to configure a custom python version installed by something like pyenv.
Using pyenv, you can install multiple python versions side-by-side without overwriting the system python, yet maintain application specific python versions.
The linked PR will solve this by utilizing a variable in
python::pyvenvcalledpython_path. If set, it will override the python version used to create that specific virtual environment.The text was updated successfully, but these errors were encountered: