Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

virtualenv and nodeenv interfere with each other #6

seibert opened this Issue Sep 24, 2011 · 5 comments


None yet
3 participants

seibert commented Sep 24, 2011

If a Python virtualenv is active and then you activate a nodeenv, you lose the virtualenv. This can be especially confusing if you installed the nodeenv python script into a Python virtualenv.

I think the problem is that nodeenv's activate script uses the same shell variable names as the Python virtualenv.


ekalinin commented Sep 26, 2011

Yes, you're right. Problem exists and is very actual.
I'll try to fix in the near future.

Thanks for report.


Lispython commented Sep 26, 2011

ekalinin, as i can see seibert already create it seibert/nodeenv@a0dcb71


ekalinin commented Sep 26, 2011

@Lispython, i think @seibert wrote about another thing.
This new feature (a0dcb71) is also very usefull.

And @seibert said that the need to globally change the variable names in activation script, as i can see.


seibert commented Sep 26, 2011

That patch is for a slightly different problem (although more directly related to my needs). The patch lets you make one combined environment directory for Python and node.js.


ekalinin commented Nov 3, 2011

Fixed in 7284982.

@ekalinin ekalinin closed this Nov 3, 2011

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment