Leo coming soon. Question for Matt.

[Edward K. Ream]

This page lists the four remaining issues scheduled for 6.0.

Matt, what's your schedule for fixing the two issues labeled "pip"?

I'll likely fix the two bugs today.

Edward

[Matt Wilkie]

Matt, what's your schedule for fixing the two issues labeled "pip"?

One is fixed (leo-console script on Windows). Desktop Links I need to break into sub-tasks, especially Linux portion. Windows part is 80% complete.

-matt

[Edward K. Ream]

On Thu, Jul 11, 2019 at 4:52 PM Matt Wilkie <map...@gmail.com> wrote:

Matt, what's your schedule for fixing the two issues labeled "pip"?

One is fixed (leo-console script on Windows). Desktop Links I need to break into sub-tasks, especially Linux portion. Windows part is 80% complete.

Thanks for the update.

Edward

[Viktor Ransmayr]

Hello Edward,

Do you plan to create a 6.0 beta 2 - or - do you plan to directly go to 6.0 final?

With kind regards.

Viktor

[Edward K. Ream]

On Fri, Jul 12, 2019 at 3:04 PM Viktor Ransmayr <viktor....@gmail.com> wrote:

> Do you plan to create a 6.0 beta 2 - or - do you plan to directly go to 6.0 final?

I expect to go directly to 6.0 final unless significant new issues arise.

Edward

[Viktor Ransmayr]

Hello Edward, hello Matt,

Installing Leo-devel via pip from GitHub into a new VE still does not work.

I've upgraded to Python 3.7.4 on Windows 10 version 1903 - however - Leo in this new VE is **still** unusable :-(

For example I'm not able to copy/paste from the Log pane to here :-((

Writing the relevant log pane content by hand:

...

current dir: C:/Users/Viktor/pyve/GitHub/Leo-devel

load dir: C:/users/viktor/pyve/github/leo-deve/lib/site-packages/leo(core

global config dir: None <- ???

home dir: C/Users/Viktor

...

No @menu setting found <- ???

...

With kind regards,

Viktor

[Viktor Ransmayr]

Hello Edward, hello Matt,

Now that Leo 6.1 is coming up, I tried again to use Leo-Dev in a dedicated Python Virtual Environment (PyVE) downloaded from GitHub & installed using pip.

I'm running again into the same - or - a very similar situation.

As you can see from my worklog, this time the current instance of Leo (let's call it Leo-stable) was explicitly closed before I started the new instance of Leo-devel.

Any idea or recommendation what to try next? - Below's the worklog I'm talking about ...

###

Check out the current PyVE setup related to Leo ...

* See "Log-001" & "Log-002".

Update PyVE "Leo-devel" to use the latest version of Leo's development branch ...

* See "Log-003"

*** Note: Close the currently running instance of Leo in PyVE "Leo"  - and - try to run the newly activated one in PyVE "Leo-devel" ***

Now Leo again reports that it doesn't find the '@menu' setting. - Unable to create a new node in the re-opened outlines ...

###

 With kind regards,

Viktor

[Viktor Ransmayr]

Hello Edward, hello Matt,

Am Sonntag, 22. September 2019 23:01:41 UTC+2 schrieb Viktor Ransmayr:

Hello Edward, hello Matt,

Am Samstag, 13. Juli 2019 17:07:44 UTC+2 schrieb Viktor Ransmayr:

Hello Edward, hello Matt,

...

Installing Leo-devel via pip from GitHub into a new VE still does not work.

...

Now that Leo 6.1 is coming up, I tried again to use Leo-Dev in a dedicated Python Virtual Environment (PyVE) downloaded from GitHub & installed using pip.

I'm running again into the same - or - a very similar situation.

As you can see from my worklog, this time the current instance of Leo (let's call it Leo-stable) was explicitly closed before I started the new instance of Leo-devel.

Any idea or recommendation what to try next?

I'm trying to follow the suggestion from Edward concerning the quality of bug reports/ inquiries. - Therefore let me re-start with a question:

Should it be possible to upgrade Leo in a given Python Virtual Environment from one Git revision to another one using the command "pip install https://github.com/leo-editor/leo-editor/archive/devel.zip --upgrade"?

If you confirm that this is a supported workflow, than I'll invest all the time necessary to resolve this issue ...

With kind regards,

Viktor

[Edward K. Ream]

On Mon, Sep 23, 2019 at 12:49 AM Viktor Ransmayr <viktor....@gmail.com> wrote:

Should it be possible to upgrade Leo in a given Python Virtual Environment from one Git revision to another one using the command "pip install https://github.com/leo-editor/leo-editor/archive/devel.zip --upgrade"?

Good question.  I'll let Matt answer it, if he can.

Edward

[Matt Wilkie]

Sorry, I can't see. The log files seem to have been stripped from https://groups.google.com/d/msg/leo-editor/lshKKfYbILM/546TIe5KBgAJ

 

Should it be possible to upgrade Leo in a given Python Virtual Environment from one Git revision to another one using the command "pip install https://github.com/leo-editor/leo-editor/archive/devel.zip --upgrade"?

Yes I expect that to work, but I haven't tested "in place upgrade from remote zip ball". I tend to download the archive first and/or `pip uninstall leo && pip install ...`. Go ahead and open a new issue and we'll see what can be figured out. Please include output of:

pip show leo
leo --version

-matt

[Viktor Ransmayr]

Hello Matt,

Am Di., 24. Sept. 2019 um 17:55 Uhr schrieb Matt Wilkie <map...@gmail.com>:

Sorry, I can't see. The log files seem to have been stripped from https://groups.google.com/d/msg/leo-editor/lshKKfYbILM/546TIe5KBgAJ

 

Should it be possible to upgrade Leo in a given Python Virtual Environment from one Git revision to another one using the command "pip install https://github.com/leo-editor/leo-editor/archive/devel.zip --upgrade"?

Yes I expect that to work, but I haven't tested "in place upgrade from remote zip ball". I tend to download the archive first and/or `pip uninstall leo && pip install ...`.

Thanks for the confirmation. - I'll set up a new Python Virtual Environment for that - and - start from scratch to have everything properly documented.

It might take a while, but I'll get back here as soon as I have something to report.

With kind regards,

Viktor