Activate shouldn't touch HOME variable #1

Activity

1. matin commented on Jan 26, 2011

   

   matin

   on Jan 26, 2011

   More actions

   +50. I use virtualenv in python religiously, and I'm working on a Ruby client. For now, I keep the following in my ~/.profile, which mirror workon from virtualenvwrapper:

   function rbworkon () {
       home=${HOME};
       source ~/.sandbox/${1}/bin/activate_sandbox;
       export HOME=${home};
   }
   
2. jhermann commented on Sep 14, 2017

   

   jhermann

   on Sep 14, 2017

   More actions

   It's not a problem for deployment use with a dedicated user, but for personal use it's a KO criterion. Especially since that also likely means you cannot use specific bang-paths for "run under" behaviour like with virtualenv.
3. jhermann commented on Sep 14, 2017

   

   jhermann

   on Sep 14, 2017

   Last edited by jhermann

   More actions

   Also, the README should explain why this is ‘better’ than RVM gem sets, or rbenv.