Replies: 1 comment 2 replies
-
@JDLH I believe that the symlinking is done by the virtualenv library when pipenv invokes it to create a non-existent virtualenv. I am not sure if other options are available when invoking that. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Is there a way to tell pipenv to copy, rather than make a symlink to, the Python interpreter when creating a virtual environment?
I have some venvs I set up with pipenv in May 2022, where the
python
executable in the venv's./bin/
directory is a copy of the original file. Venvs I set up in June and 2022 have a symbolic link from./bin/python
to the actual file.My current version of pipenv is 2022.5.2. It is possible that on 10 May 2022 I was using an earlier version of pipenv.
The reason why I want a copy of the interpreter file is that I am using a Python IDE, PyDev, which apparently resolves all symbolic links to interpreters into the absolute path to the actual file. And, it lets me use each absolute interpreter path for only one project. Thus when I create multiple venvs which link to the same interpreter executable, it refuses let me configure the subsequent projects to use the venv. I would like it if they changed this behaviour. But until they do, my workaround is to have pipenv copy the Python interpreter executable file, instead of linking to it.
I am aware that issue #2108 Virtualenv created includes copy of python exectuable made essentially the opposite case. I guess there is no one default which will please everyone.
Beta Was this translation helpful? Give feedback.
All reactions