On Fri, Feb 2, 2018 at 4:02 PM, Edward K. Ream wrote:
This is great stuff, because now I only need one version of scripts
>
Even better, there is now only one version of the conda and pip commands,
no matter how many environments there are.
Edward
--
You received this message because you are
On Fri, Feb 2, 2018 at 4:20 PM, Terry Brown wrote:
> On Fri, 2 Feb 2018 14:02:08 -0800 (PST)
> "Edward K. Ream" wrote:
>
> > The only strange thing so far is that the Miniconda installer
> > recommended *not* putting Miniconda3 on the path.
>
> Perhaps it feels it's impolite to modify the path a
On Fri, 2 Feb 2018 14:02:08 -0800 (PST)
"Edward K. Ream" wrote:
> The only strange thing so far is that the Miniconda installer
> recommended *not* putting Miniconda3 on the path. Actually, it's
> essential to do so, unless you use the Miniconda console. And you
> have to put both Miniconda3 an
On Friday, February 2, 2018 at 12:11:19 PM UTC-6, Edward K. Ream wrote:
> This is totally unacceptable.
Heh. This has turned into a lucky break.
I replaced both Anaconda2 and Anaconda3 with (32-bit) Miniconda3. I chose
32-bit so that the spell checker will work.
I created python2 and python
On Fri, Feb 2, 2018 at 1:00 PM, Terry Brown wrote:
p.s. I just recently saw a tweet that claimed you could create a
> Python 1.0 environment, which prompted a "Wait, what?" tweet from
> Guido, but I'm not sure if that's true or an old April Fool's gag.
>
Hehe.
Edward
--
You received this mes
On Fri, Feb 2, 2018 at 12:58 PM, Terry Brown wrote:
>
> > Won't I have to install lots of packages if I use miniconda?
>
> I guess it would be interesting to know exactly what's on the list of
> packages you'd need.
>
it would indeed be good to know what the minimal packages are .
> I think
On Fri, 2 Feb 2018 12:53:12 -0600
"Edward K. Ream" wrote:
> > Python 2 and Python 3 installs can create environments that use the
> > other version of Python, i.e. a Python 3 environment can be created
> > by Python 2 based conda, and visa versa.
>
> This is fascinating. It would be a major ch
On Fri, 2 Feb 2018 12:53:12 -0600
"Edward K. Ream" wrote:
> Won't I have to install lots of packages if I use miniconda?
I guess it would be interesting to know exactly what's on the list of
packages you'd need.
I think the recommended way to install them is
conda install -c conda-forge
whic
On Fri, Feb 2, 2018 at 12:43 PM, Terry Brown wrote:
Hmm, if Anaconda's the source of Python on your system, not sure if it
> makes sense to install virtualenv "in" Anaconda. conda can manage
> environments itself, like virtualenv, and I'd expect things to get
> weird if you mix them.
Ah. I s
On Fri, 2 Feb 2018 10:11:19 -0800 (PST)
"Edward K. Ream" wrote:
> My original system contains c:\Anaconda2 and c:\Anaconda3. I
> installed virtualenv with both pip2 and pip3.
Hmm, if Anaconda's the source of Python on your system, not sure if it
makes sense to install virtualenv "in" Anaconda.
On Friday, February 2, 2018 at 12:11:19 PM UTC-6, Edward K. Ream wrote:
My original system contains c:\Anaconda2 and c:\Anaconda3. I installed
> virtualenv with both pip2 and pip3.
>
> I did a virtualenv c:\Env\Test which only partially worked as expected.
> No scripts were installed. No obv
My original system contains c:\Anaconda2 and c:\Anaconda3. I installed
virtualenv with both pip2 and pip3.
I did a virtualenv c:\Env\Test which only partially worked as expected. No
scripts were installed. No obvious way to do deactivate.
Worse, C:\Anaconda3 no longer contains python.exe. M
12 matches
Mail list logo