News for hackers. Stuff that matters.
Re:Creating Python Virtual Environments with Conda: Why and How by jhrmnn on Tuesday December 10, 2019 @02:34PM (#21756009)
Conda virtual environments and Pip are orthogonal. Pip can be used to install into venvs. But as to why use conda rather than just the standard library venv module (python3 -m venv venv): conda can easily manage multiple python versions. In my experience, it's the most hassle-free option compared to something like pyenv. I personally use conda just for managing venvs, and don't use its package manager functionality at all.
Re:Creating Python Virtual Environments with Conda: Why and How by dfsegoat on Tuesday December 10, 2019 @03:02PM (#21756274)
FWIW our use case is the same:

- Conda to manage multiple python versions on 1 box:

  $ conda create -n env27 python=2.7
  $ conda create -n env37 python=3.7

- Pip to manage packages in the environment:

  $ source activate env27
  $ pip install -r requirements_27.txt
Re:Creating Python Virtual Environments with Conda: Why and How by qwerty456127 on Wednesday December 11, 2019 @06:48PM (#21768013)
But why would anybody need a Python version other than the latest? Aren't they backward-compatible within a major version? Won't everything written for Python 3.7 work on 3.8 and everything written for 2.6 work on 2.7?