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 control of venv creation mode --copies vs. --symlinks #1230

Closed
jsirois opened this issue Feb 7, 2021 · 1 comment · Fixed by #1245
Closed

Support control of venv creation mode --copies vs. --symlinks #1230

jsirois opened this issue Feb 7, 2021 · 1 comment · Fixed by #1245
Assignees

Comments

@jsirois
Copy link
Member

jsirois commented Feb 7, 2021

Currently venvs created by Pex use the default creation mode of the venv or virtualenv module depending on which is used. The venv module supports forcing --copies or --symlinks for Python3.5+ and the virtualenv module we vendor supports --always-copy (there is no correspnding --always-symlink).

@jsirois jsirois mentioned this issue Feb 7, 2021
6 tasks
@jsirois jsirois self-assigned this Feb 16, 2021
@jsirois
Copy link
Member Author

jsirois commented Feb 16, 2021

This was spurred by pantsbuild/pants#11531 where Pants could use the --copies mode once it solves internal speed problems with (re-)storing the contents of a venv.

jsirois added a commit to jsirois/pex that referenced this issue Feb 22, 2021
Add support for creating venvs using copies instead of symlinks.

Fixes pex-tool#1230
jsirois added a commit that referenced this issue Feb 22, 2021
Add support for creating venvs using copies instead of symlinks.

Fixes #1230
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant