VIRTUAL_ENV var
Oscar
We are working on workflow where we share our virtualenvwrappers files
using our network, so I found an issue in this scenario, and it is the
VIRTUAL_ENV environment var, so if I create the VEW this var keeps my
path in other user machines, so I need that it changes it value and
depends on the machine that invoke that VEW. So how I can do that?
Best regards,
Oscar.
Doug Hellmann
I'm not sure I understand exactly what you want, so let me try restating it and see if I have it.
You have multiple environments, and use them on multiple computers. When you change the active virtualenv on one computer, you want it to also change the active virtualenv on another computer.
Is that right?
What operating system(s)?
I don't know of a good way to do that under Unix. It isn't normally possible to change the environment settings of a process from outside of that process (except from the parent, at the point when the child process is created). There are a lot of security reasons for that, but it would also be tricky to implement reliably.
Rather than focusing on this specific technical issue, why don't you describe the goal you eventually hope to achieve by doing this, and maybe we can find a different solution.
Doug
Oscar A. Mata T.
--
Oscar A. Mata T.
Doug Hellmann
On Jul 3, 2011, at 1:18 PM, Oscar A. Mata T. wrote:
> Nope,
>
> Before hand, sorry because I'm not english speaking person, said that:
That's not a problem.
>
> I have a single VEW shared using Dropbox, 5 users must use this single VEW but the VIRTUAL_ENV var keeps the original value from the user that created it. So I need that the VIRTUAL_ENV var get the right value from another environment variable pre-configured in each workstation and let the wrapper work as expected.
OK, that is clear. It may be possible to do what you want, with some conditions.
>
> I'm using right now OSX and Ubuntu, no Windows machines here.
If you want to share the virtualenv between OS X and Ubuntu, you will have trouble. The binary for the Python interpreter is copied to bin/python within the virtualenv. That binary won't run on both platforms. If you don't care about sharing between operating systems, ignore this.
virtualenv supports a "relocatable" mode, which does not embed the path to the environment inside the files contained in the environment. The purpose for that feature, as I understand it, is to move the environment using normal commands like mv and cp. It may help in your case, too. I don't use the feature myself, but the people on the virtualenv mailing list should be able to give you guidance about how to turn it on and what issues might come up as a result.
Hope that helps,
Doug
Oscar A. Mata T.
--
Oscar A. Mata T.