Anaconda and Leo

[Largo84]

I recently had to reinstall Leo on my assistant's PC after a computer upgrade. I was sorta dreading the experience, but found that the Anaconda route was actually pretty easy. However, I have a documentation comment and a question:

1. Following the instructions, I tried the pip install leo command in the Anaconda console, but got a permissions error. I had to run the Console command as an Administrator (right-cick and select). Perhaps that should be added to the Leo docs as it may not be obvious to others (it wasn't to me at first)?
2. On my own machine, I always run Leo from a GitHub directory so I can run the most current version. What about on her machine? How does Anaconda work to keep Leo updated?

Rob...

[Edward K. Ream]

On Mon, Feb 12, 2018 at 7:06 AM, Largo84 <lar...@gmail.com> wrote:

I recently had to reinstall Leo on my assistant's PC after a computer upgrade. I was sorta dreading the experience, but found that the Anaconda route was actually pretty easy.

​Good to hear.
​

 

However, I have a documentation comment and a question:

1. Following the instructions, I tried the pip install leo command in the Anaconda console, but got a permissions error. I had to run the Console command as an Administrator (right-cick and select). Perhaps that should be added to the Leo docs as it may not be obvious to others (it wasn't to me at first)?

​I'll put this on the list for Leo 5.7 final.  It's too late to mess with the installation docs now.  Btw, I am still dithering what to do about Matt's suggestions.

Expect 5.7 final on Friday.  We should have plenty of time to deal with last remaining issues, including documentation, by then.​

1. On my own machine, I always run Leo from a GitHub directory so I can run the most current version. What about on her machine? How does Anaconda work to keep Leo updated?

​It doesn't.  If you install Leo from Anaconda you are using the last version of Leo that Anaconda knows about, not the latest github version.  So if you are using git to keep Leo up to date (as you should ;-) you should not install Leo using Anaconda.​

HTH

Edward

[Chris George]

From scratch, I install Anaconda and then install Leo using git. I start Leo using a shell script in a terminal that pulls the latest code, runs launchLeo.py --session-restore --session-save, then commits any changes in checked in Leo files to fossil once Leo is shut down.

This keeps me up to date.

Chris

--
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 leo-editor+unsubscribe@googlegroups.com.
To post to this group, send email to leo-e...@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

[Largo84]

So, is there an Anaconda update command that will pull in a more recent 'official' release? Or, is her machine stuck with whichever version was installed initially? Or would I need to manually update her Leo package in Anaconda whenever I think it's advantageous to do so?

Rob...

[Matt Wilkie]

So, is there an Anaconda update command that will pull in a more recent 'official' release? Or, is her machine stuck with whichever version was installed initially? Or would I need to manually update her Leo package in Anaconda whenever I think it's advantageous to do so?

 
Just to clarify, Anaconda isn't for installing Leo, it's for installing a python and all Leo's dependencies that doing manually is a pain. Pip is the package manager for installing Leo itself and will be included in any recent install of python.

After installing Anaconda (I suggest Miniconda for the scenario you describe. Less to download)  upgrading Leo is straightforward.

Upgrade to latest version published on PyPi.org (so, latest milestone release):

pip install --upgrade leo

Upgrade to current development version:

pip install --upgrade https://github.com/leo-editor/leo-editor/archive/master.zip

Upgrade to any tag in the development version (after ~Dec 2017, earlier tags will probably fail):

pip install --upgrade https://github.com/leo-editor/leo-editor/archive/5.7b2.zip

Matt

[Matt Wilkie]

Upgrade to any tag in the development version (after ~Dec 2017, earlier tags will probably fail):

pip install --upgrade https://github.com/leo-editor/leo-editor/archive/5.7b2.zip

Sigh. One of these days I'll learn to test my examples! This particular one breaks with bug related to issue #691. It will work by the time 5.7 is released and should remain stable after that.

Matt

[Matt Wilkie]

Upgrade to any tag in the development version (after ~Dec 2017, earlier tags will probably fail):

pip install --upgrade https://github.com/leo-editor/leo-editor/archive/5.7b2.zip

Sigh. One of these days I'll learn to test my examples! This particular one breaks with bug related to issue #691. It will work by the time 5.7 is released and should remain stable after that.

It's actually a new bug: https://github.com/leo-editor/leo-editor/issues/720

matt

[Edward K. Ream]

On Mon, Feb 12, 2018 at 8:44 PM, Largo84 <lar...@gmail.com> wrote:

So, is there an Anaconda update command that will pull in a more recent 'official' release?

​`conda update leo` should do this.  However, what you are calling the latest "official" release is the latest Anaconda package for Leo.  This has nothing whatever to do with the latest git rev.  Clear?

Edward

[Largo84]

Yes, got it, thanks for clarifying. That's kinda what I thought, but wasn't sure.

Rob...