On Sat, Mar 28, 2020 at 11:13 PM Matt Wilkie <[email protected]> wrote:
If you install Leo (or whatever) into the base environment instead of > creating a distinct envs for projects you can get the simplicity of a > single system environment, similar to installing python the regular way, > and still use the conda package manager (if that's a desirable thing for > your work). > > In this case add the base env bin to PATH so it's always available or use > the system menu 'Anaconda Prompt' (which is the same as `activate` with no > env specified). > > It should be noted this goes against the grain of Anaconda's design and > they recommend against it. Still works though! > Thanks for these comments. Imo, Anaconda has become harder to use in the last year or so. Not sure why. *Aha*: Now that Leo requires python 3, we can assume pip is always available. (Actually, people may have to use apt-get on Linux to get pip3.) In my recent experience, pip is easier to use and more solid than conda. Ymmv. I am seriously considering ignoring Anaconda and miniconda in Leo's installation instructions: Install python 3 (ubuntu) apt-get install pip3 pip install PyQt5 (optional, if not using git) pip install leo And that's it. Comments? Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/CAMF8tS339qXkd%3DDeYWOWnE3g4o%3Dy_kP0zMYke3OK%3DmhzUtX6wA%40mail.gmail.com.
