[conda] Alternative to `source activate`

[Paolo Di Tommaso]

Dear community,

I've noticed that some users instead of activating an environment with the
`source activate <name>` command, they just add the environment bin
directory to the PATH.

Is the reany drawback in this practice? Is it 100% equivalent to activating
the env with the source activate command?


Thanks in advance.

Cheers,
Paolo

[Paul Hobson]

I typically have 10 - 15 environments that I use on a regular basis.

Manually managing the PATH sounds like a huge headache to me.
-paul

Post by Paolo Di Tommaso
Dear community,
I've noticed that some users instead of activating an environment with the
`source activate <name>` command, they just add the environment bin
directory to the PATH.
Is the reany drawback in this practice? Is it 100% equivalent to
activating the env with the source activate command?
Thanks in advance.
Cheers,
Paolo
--
You received this message because you are subscribed to the Google Groups
"conda - Public" group.
To unsubscribe from this group and stop receiving emails from it, send an
Visit this group at https://groups.google.com/a/continuum.io/group/conda/.
To view this discussion on the web visit https://groups.google.com/a/
continuum.io/d/msgid/conda/0ab4fa87-c2ef-4ada-ac90-
818614033dc3%40continuum.io
<https://groups.google.com/a/continuum.io/d/msgid/conda/0ab4fa87-c2ef-4ada-ac90-818614033dc3%40continuum.io?utm_medium=email&utm_source=footer>
.
For more options, visit https://groups.google.com/a/continuum.io/d/optout.

[Lori Burns]

I manage the PATH by hand rather than `conda|source activate` about a
quarter of the time. It's useful when combining lots of software only parts
of which are managed by conda or which require separate conda envs. Also
useful to reconcile hard-core linux people that conda is doing sense, not
magic. It's always worked nicely for me. I believe it's equivalent except
that when there are envvar or activate/deactivate scripts associated with
the environment. So I wouldn't want to just alter PATH and expect to use
the new {lang}-{target_platform} compilers. And perhaps newer conda has
other features that happen upon activation that I'm not familiar with.

Post by Paolo Di Tommaso
Dear community,
I've noticed that some users instead of activating an environment with the
`source activate <name>` command, they just add the environment bin
directory to the PATH.
Is the reany drawback in this practice? Is it 100% equivalent to
activating the env with the source activate command?
Thanks in advance.
Cheers,
Paolo