[CentralOH] Conda Versus Virtualenv
pybokeh at gmail.com
Sat Nov 22 21:03:29 CET 2014
If you are on Windows machine and will be using numpy/scipy, definitely use
conda over virtualenv/pyvenv. On Linux, if you don't mind waiting longer
to install packages, then sure go right ahead and use virtualenv/pyvenv
over conda. You will then have the latest version of the packages in the
Virtualenv/pyven and conda are similar except with conda, it has
pre-compiled packages that it just downloads and then installs right from
the get-go. So no compilation step, no need to have C or Fortran
compilers. With virtualenv/pyvenv depending on the package, there's an
additional and longer compilation step.
So if you're using Linux machine and not using packages that depend on C or
Fortran compilation, maybe there isn't too much advantage to using conda
over virtualenv/pyvenv. But conda has some nifty commands that make it
easy to create a python 2 vs python 3 environment. For example, if you
install conda installation for python 3, you can still create a python 2
environment by just adding python=2 or python=2.7 in the conda command (
http://continuum.io/blog/anaconda-python-3). I can see if you just want to
stick with the tooling that comes with your default Python installation
that you would just stick with pyvenv instead of having to install a 3rd
party package management system like Anaconda/conda. But for me, I just
got tired of the hassle with compiling.
For a list of packages that are available by default by conda:
CAVEAT: I've only been using Python for maybe 4 or 5 yrs and Linux even
less, so I could be wrong with the details. I'm sure a Python veteran can
better explain or correct me. All I know for sure, if you're using Windows
and need to make Python virtual environments, you really have no choice but
On Nov 22, 2014 2:04 PM, "John Santiago" <jdsantiagojr at gmail.com> wrote:
> This is the first time I have heard of conda. Would you reccommend using
> it over venv. What are some of the advantages over venv?
> On Nov 22, 2014 12:34 PM, "pybokeh" <pybokeh at gmail.com> wrote:
>> I have been using conda/miniconda on Windows at work and
>> virtualenv/pyvenv at home on Linux machine.
>> But on my Linux machine, I have dropped pyvenv recently and just use
>> miniconda for now on.
>> It saves so much time from having to compile the source and the
>> miniconda/Anaconda distribution
>> has most of the packages I need. For packages it doesn't have, I can
>> still use pip to install them.
>> The only disadvantage I can think of using miniconda is maybe you have to
>> wait a week or two longer
>> to get the latest and greatest version of a package or when a new version
>> of Python comes out, you'll
>> have to wait even longer still. But that's minor IMO.
>> On Mon, Nov 17, 2014 at 6:39 PM, <jep200404 at columbus.rr.com> wrote:
>>> On Mon, 17 Nov 2014 10:16:26 -0500, Eric Floehr <eric at intellovations.com>
>>> [> On Mon, 17 Nov 2014 09:55:41 -0500, jep200404 at columbus.rr.com wrote:]
>>> > > What's best way to install ... _and_ virtualenv?
>>> > ... uses conda as the package and environment manager.
>>> What do you think of conda versus virtualenv?
>>> Would you drop (or have you dropped) virtualenv to use conda instead?
>>> CentralOH mailing list
>>> CentralOH at python.org
>> CentralOH mailing list
>> CentralOH at python.org
> CentralOH mailing list
> CentralOH at python.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the CentralOH