Please test Leo 6.4 at pypi

[Edward K. Ream]

It's here. I added this link to leoInteg.

Please report any problem immediately. I plan to announce Leo 6.4 widely tomorrow.

Edward

[tbp1...@gmail.com]

The distro at Pypi identifies itself as 6.4-devel.  Better change that!

Leo 6.4-devel

Python 3.9.5, PyQt version 5.15.2

Windows 10 AMD64 (build 10.0.19043) 

[Edward K. Ream]

On Thu, Sep 23, 2021 at 8:43 AM tbp1...@gmail.com <tbp1...@gmail.com> wrote:

The distro at Pypi identifies itself as 6.4-devel.  Better change that!

Oops.  I wonder whether I did the second build in the right branch.

I've just tried again.  Btw, how do you invoke the installed Leo?

Edward

[tbp1...@gmail.com]

python3 -m leo.core.runLeo # PYTHONPATH has not been set.

For running branches from my git clone, I use a batch file to set PYTHONPATH to point to the clone and then run the same command.

Installed with

python3 -m pip install --upgrade leo

[tbp1...@gmail.com]

Still getting those error messages when opening LeoPyRef.leo:

can not open C:/Users/tom/AppData/Roaming/Python/Python39/site-packages/leo_to_html.xsl

can not open C:/Users/tom/AppData/Roaming/Python/Python39/site-packages/run_travis_unit_tests.py

file not found: C:/Users/tom/AppData/Roaming/Python/Python39/site-packages/launchLeo.py

can not open C:/Users/tom/AppData/Roaming/Python/Python39/site-packages/run_pytest_tests.py

can not open C:/Users/tom/AppData/Roaming/Python/Python39/site-packages/setup.py

can not open C:/Users/tom/AppData/Roaming/Python/Python39/site-packages/flake8-leo.py

can not open C:/Users/tom/AppData/Roaming/Python/Python39/site-packages/pyflakes-leo.py

can not open C:/Users/tom/AppData/Roaming/Python/Python39/site-packages/pylint-leo.py

[Edward K. Ream]

On Thu, Sep 23, 2021 at 11:02 AM tbp1...@gmail.com <tbp1...@gmail.com> wrote:

Still getting those error messages when opening LeoPyRef.leo:

can not open C:/Users/tom/AppData/Roaming/Python/Python39/site-packages/leo_to_html.xsl

can not open C:/Users/tom/AppData/Roaming/Python/Python39/site-packages/run_travis_unit_tests.py

file not found: C:/Users/tom/AppData/Roaming/Python/Python39/site-packages/launchLeo.py

can not open C:/Users/tom/AppData/Roaming/Python/Python39/site-packages/run_pytest_tests.py

can not open C:/Users/tom/AppData/Roaming/Python/Python39/site-packages/setup.py

can not open C:/Users/tom/AppData/Roaming/Python/Python39/site-packages/flake8-leo.py

can not open C:/Users/tom/AppData/Roaming/Python/Python39/site-packages/pyflakes-leo.py

can not open C:/Users/tom/AppData/Roaming/Python/Python39/site-packages/pylint-leo.py

I see those messages too. Imo, they are both expected and harmless.

Edward

[Edward K. Ream]

On Thu, Sep 23, 2021 at 10:43 AM tbp1...@gmail.com <tbp1...@gmail.com> wrote:

python3 -m leo.core.runLeo # PYTHONPATH has not been set.

Thanks.

Running `python3 -m leo.core.runLeo`:

- If I run it from the leo-editor folder then python will launch Leo from whatever branch is checked out.

- Otherwise, python will launch the installed version of Leo, if any.  And I see Leo 6.4 as expected in the log.

In short, the pypi version of Leo is correct.

Edward

[Viktor Ransmayr]

Hello Thomas,

Am Do., 23. Sept. 2021 um 18:02 Uhr schrieb tbp1...@gmail.com <tbp1...@gmail.com>:

Still getting those error messages when opening LeoPyRef.leo:

can not open C:/Users/tom/AppData/Roaming/Python/Python39/site-packages/leo_to_html.xsl

can not open C:/Users/tom/AppData/Roaming/Python/Python39/site-packages/run_travis_unit_tests.py

file not found: C:/Users/tom/AppData/Roaming/Python/Python39/site-packages/launchLeo.py

can not open C:/Users/tom/AppData/Roaming/Python/Python39/site-packages/run_pytest_tests.py

can not open C:/Users/tom/AppData/Roaming/Python/Python39/site-packages/setup.py

can not open C:/Users/tom/AppData/Roaming/Python/Python39/site-packages/flake8-leo.py

can not open C:/Users/tom/AppData/Roaming/Python/Python39/site-packages/pyflakes-leo.py

can not open C:/Users/tom/AppData/Roaming/Python/Python39/site-packages/pylint-leo.py

This is all related to the fact that anything in the root folder of the leo-editor code repository is not installed when using pip.

It has been reported by me a long time ago & analyzed by Matt Wilkie in detail. - See

* https://github.com/leo-editor/leo-editor/issues/603

With kind regards,

Viktor

[tbp1...@gmail.com]

Aha, I found the source of the discrepancy.  I had installed Leo to the system site-packages directory and not the user one.  The user location had a 6.4b3 installation.  I though that the system location would take precedence, but apparently not.  After I deleted the 6.4b3 directories, I get 

Leo 6.4

Python 3.9.5, PyQt version 5.15.2

Windows 10 AMD64 (build 10.0.19043) 

as expected.

[tbp1...@gmail.com]

Maybe I just never noticed it before...

[Edward K. Ream]

On Thu, Sep 23, 2021 at 12:07 PM Viktor Ransmayr <viktor....@gmail.com> wrote:

This is all related to the fact that anything in the root folder of the leo-editor code repository is not installed when using pip.

Exactly.

It has been reported by me a long time ago & analyzed by Matt Wilkie in detail. - See

* https://github.com/leo-editor/leo-editor/issues/603

Thanks, Victor, for the reminder. And thanks, Thomas, for your careful testing and reporting.

Edward

[Edward K. Ream]

On Thu, Sep 23, 2021 at 12:20 PM tbp1...@gmail.com <tbp1...@gmail.com> wrote:

Aha, I found the source of the discrepancy.  I had installed Leo to the system site-packages directory and not the user one.  The user location had a 6.4b3 installation.  I though that the system location would take precedence, but apparently not.  After I deleted the 6.4b3 directories, I get 

Leo 6.4

Python 3.9.5, PyQt version 5.15.2

Windows 10 AMD64 (build 10.0.19043) 

as expected.

Thanks for the report!

Edward