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

--always-copy flag doesn't copy #654

Closed
joedborg opened this issue Sep 29, 2014 · 3 comments
Closed

--always-copy flag doesn't copy #654

joedborg opened this issue Sep 29, 2014 · 3 comments

Comments

@joedborg
Copy link

$ python2.7
Python 2.7.6 (default, Nov 18 2013, 11:08:31) 
[GCC 4.4.6 20120305 (Red Hat 4.4.6-4)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import django
>>>

$ find /usr/local/lib/python2.7/site-packages -name "*django*"
# Lots of files listed.

$ virtualenv-2.7 --system-site-packages --always-copy django_branch

$ find ./django_branch/ -name "*django*"
# Nothing found.
@dstufft dstufft mentioned this issue Jan 5, 2015
5 tasks
@ionelmc
Copy link

ionelmc commented Jan 5, 2015

In the current virtualenv incarnation --always-copy is meant for the bootstrap modules (and include dir perhaps).

For what @joedborg is asking, it essentially mean relocating modules from the global site-packages. I don't think this can be fixed (especially if we drop the relocatable support from the rewrite). Perhaps close this, @dstufft ?

@joedborg, what's your use-case for this?

@joedborg
Copy link
Author

joedborg commented Jan 5, 2015

Hi @ionelmc, I was basically looking for a way of copying a Python instance, to then use for testing (e.g. copy it to a test server or update a package and test).

I didn't think this would be fixed here (although having the flag in virtualenv leads one to believe that it works), so I have started a project (https://josephb.org/projects/vampire/) to create something for this. Any help with the project would be greately received.

@stale
Copy link

stale bot commented Jan 15, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Just add a comment if you want to keep it open. Thank you for your contributions.

@stale stale bot added the wontfix label Jan 15, 2019
@stale stale bot closed this as completed Jan 22, 2019
@pypa pypa locked and limited conversation to collaborators Jan 14, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants