Bottom Page

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
 Why is virtualenv not by default relocatable?
I'm working in a system (not my choice) where the code lives on a dropbox, and everyone runs from the shared dropbox. I can't change that, so don't bother to suggest it.

Now, the problem is that everyone's dropbox is mounted in their home-directory (I can't change that either). So, if I put the virtualenv on the dropbox, everyone will have a different path.

My question is: Why is this hard? Why are all paths in a virtualenv not relative to the virtualenv directory? I understand that some things may need to be in /usr/local, or whatever, so everyone may still need to have python installed on their computer, but why do I need to manually search and replace all /users/brianp with $HOME? I first ran with --relocatable, but that doesn't change any 'normal script file'

Alternatively: What massive failure mode am I inviting with this architecture? and is there a better way to do this that doesn't require each user to maintain their own copy of the venv?
*IF* I could convince everyone to move their dropbox mountpoint to / or /Volumes or something, would that solve my problem?

Top Page

Possibly Related Threads...
Thread Author Replies Views Last Post
  Installing PIP and setting up virtualenv steveholland68 1 560 Aug-08-2019, 05:52 PM
Last Post: snippsat
  python -m venv VS virtualenv kazi380 4 671 Jul-17-2019, 08:51 PM
Last Post: Larz60+
  Virtualenv and an infinitely spooling interpreter? eblade 3 572 Jul-11-2019, 06:58 PM
Last Post: eblade
  opencv without virtualenv tony1812 0 1,518 Jan-20-2018, 12:42 AM
Last Post: tony1812
  virtualenv activate.ps1 hash error po20 2 1,488 Jan-13-2018, 09:21 AM
Last Post: po20
  virtualenv on powershell mcmxl22 3 2,949 Feb-08-2017, 06:29 AM
Last Post: snippsat

Forum Jump:

Users browsing this thread: 1 Guest(s)