4 ms·

I wonder why pythonbrew gets no love - http://stacktoheap.com/blog/2013/03/11/why-use-virtualenv-when-there-is-pythonbrew/ http://stacktoheap.com/blog/2013/03/1

• robertfw 14y ago
  What pain points does pythonbrew solve? Im curious as the linked blog post was a bit light on detail
  • manojlds 14y ago
    It helps in managing pythons AND is a wrapper to virtualenv for managing environments. And it solves some pain points that virtualenvwrapper solves, like virtual environments files external to project etc. If you are from ruby / rails world, you will love and be at home with pythonbrew.
    • chrishas35 14y ago
      I used pythonbrew for a while, but as I moved into testing apps with multiple versions of python (via tox), using pythonbrew's executables became more trouble than it was worth. Because of that, I've gone back to using homebrew to compile multiple versions of python and letting tox utilize those. Homebrew takes care of pip & distribute so adding virtualenv & virtualenvwrapper is a simple oneliner after the fact.
• antihero 14y ago
  Autoenv is pretty pointless because you can assign a "project dir" to a virtualenv (and also postactivate scripts). So I can just do workon myproject and be instantly transported to the right place with the right environment.
  • manojlds 14y ago
    Is that versioned so that all you teammates do the same thing?
• pekk 14y ago
  It is much cleaner to use OS packages for the different versions of Python you need. There is no problem asking virtualenv to use a specific installed version.