3 ms·

So a stupid question about virtualenv for you. Why does it default to full paths for everything?

• obviouslygreen 13y ago
  Honestly, I have no idea. I haven't ever tried to move a virtualenv, and it's not something that's supposed to be part of your repo (you should build your env separately on every box; it's intended to encapsulate dependencies from the system, not to transfer them around with your code). If your system gets updated/upgraded to the point where your virtualenv breaks, rebuild it from scratch; all it should take is a bit of time. [edit: I am not a developer involved with virtualenv, and the statement about what it's intended for probably shouldn't be quite so strong, as this is only my impression of it and the way I use it.]
• chrisdl 13y ago
  I actually don't "know" either. But I suspect it has to do with knowing which python to use (system generally) and if the user wants to use global packages as well. checkout virtualenvwrapper (http://virtualenvwrapper.readthedocs.org/en/latest/install.html http://virtualenvwrapper.readthedocs.org/en/latest/install.h...) as well for handling virtualenvs.
  • obviouslygreen 13y ago
    +1, I definitely should have mentioned this. virtualenvwrapper makes it vastly more convenient.
  • dangoldin 13y ago
    Author here - thanks for mentioning this! I've never used it but will give it a go.