Initial F/B for installation of Leo 6.2b1 via pip from PyPI

66 views
Skip to first unread message

Viktor Ransmayr

unread,
Mar 20, 2020, 3:05:45 AM3/20/20
to leo-editor
Hello Edward, hello Matt,

Installation into a new PyVE on Debian went well - and - I did not notice any problems so far.

Here's the log after initial startup of Leo:

<Log>

Leo Log Window
Leo 6.2-b1
Python 3.7.3, PyQt version 5.12.7
linux
setting leoID from os.getenv('USER'): 'user'
current dir: /home/user/PyVE/PyPI
load dir: /home/user/PyVE/PyPI/Leo-6-2-b1/lib/python3.7/site-packages/leo/core
global config dir: /home/user/PyVE/PyPI/Leo-6-2-b1/lib/python3.7/site-packages/leo/config
home dir: /home/user
reading settings in /home/user/PyVE/PyPI/Leo-6-2-b1/lib/python3.7/site-packages/leo/config/leoSettings.leo
reading settings in /home/user/.leo/myLeoSettings.leo
reading settings in /home/user/Documents/WL2020.leo
Creating ~/.leo/spellpyx.txt
created: /home/user/.leo/spellpyx.txt
read outline in 0.09 seconds
reading settings in /home/user/.leo/myLeoSettings.leo

</Log>

Thanks a lot for all your work on it.

In the upcoming days I'll revisit the status of other issues I've reported earlier.

With kind regards,

Viktor

Edward K. Ream

unread,
Mar 20, 2020, 8:25:52 AM3/20/20
to leo-editor
On Fri, Mar 20, 2020 at 2:05 AM Viktor Ransmayr <viktor....@gmail.com> wrote:
Hello Edward, hello Matt,

Installation into a new PyVE on Debian went well - and - I did not notice any problems so far.

Thanks for the confirmation.

Edward

Thomas Passin

unread,
Mar 20, 2020, 10:49:32 PM3/20/20
to leo-e...@googlegroups.com
Success on Linux Mint on VirtualBox-

tom@tom-VirtualBox:~$ python3.6 -m pip install --upgrade leo==6.2b1

However:
Leo 6.2-b1
Creating ~/.leo/spellpyx.txt
created: /home/tom/.leo/spellpyx.txt
not found: /home/tom/.leo/d:/test/jython/unicode/punct_py.py
not found: /home/tom/.leo/d:/test/jython/unicode/punct_jy.py
not found: /home/tom/.leo/d:/test/jython/unicode/unicode_fail.py
not found: '@auto testconfig.ini'
not found: '@auto readconfig.py

tfer

unread,
Mar 21, 2020, 10:32:11 AM3/21/20
to leo-editor
I been running Leo from a local clone of 'develop' under full Anaconda, (not using env's, just adding things it complained about missing to the base site packages).  I've since gone to a miniconda base and created a conda env 'leobase'.  At some point playing with getting this barebones env to work, I found out what setup.py is for and realized I should be letting it handle this.  

Running:
./setup.py develop
in powershell, I found it bombed out due to the 'cleanup with janitor' - stuff.  I deleted the offending line and run it successfully.  Looking at the script terminal output, I see that it did this:
Searching for setupext-janitor>=1.1
Reading https://pypi.org/simple/setupext-janitor/
Downloading https://files.pythonhosted.org/packages/fe/7c/21ab50164321e657d7ca281bc827b317351b0504dca72025b1e8063d4b91/setupext_janitor-1.1.2-py2.py3-none-any.whl#sha256=9cb4b72323c58b5a691d7bbb5b44079b0171c32297634b43b3ec21452bfa68ef
Best match: setupext-janitor 1.1.2
Processing setupext_janitor-1.1.2-py2.py3-none-any.whl
Installing setupext_janitor-1.1.2-py2.py3-none-any.whl to c:\programdata\anaconda3\lib\site-packages
Adding setupext-janitor 1.1.2 to easy-install.pth file
This was using the 'develop' branch, if its 'setup.py' is the same as the release, then there is a subtle bug awaiting anyone who does not have setupext-janitor  already installed.

Tom
 

Matt Wilkie

unread,
Mar 22, 2020, 1:26:20 PM3/22/20
to leo-editor


On Saturday, 21 March 2020 07:32:11 UTC-7, tfer wrote:
I been running Leo from a local clone of 'develop' under full Anaconda, (not using env's, just adding things it complained about missing to the base site packages).  I've since gone to a miniconda base and created a conda env 'leobase'.  At some point playing with getting this barebones env to work, I found out what setup.py is for and realized I should be letting it handle this.  

Running:
./setup.py develop

It's prefered to use `pip install --editable path\to\code` over `python setup.py develop`. It has a handler for the dependencies needed just for setup (setup janitor in this instance). More importantly it registers the installed files so they can removed later with `pip uninstall {thing}`. With the `develop` method it's up to you to hunt down all the instances under PYTHONHOME site-packages, scripts, etc. and remove them. See https://stackoverflow.com/questions/30306099/pip-install-editable-vs-python-setup-py-develop

-matt

Matt Wilkie

unread,
Mar 22, 2020, 1:28:16 PM3/22/20
to leo-editor
Installation into a new PyVE on Debian went well - and - I did not notice any problems so far.

Good to hear Viktor. If I'm not mistaken this is the first trouble-free install in your environment for a number of releases. Yay :)

-matt

Matt Wilkie

unread,
Mar 22, 2020, 1:35:51 PM3/22/20
to leo-editor

not found: /home/tom/.leo/d:/test/jython/unicode/punct_py.py
not found: /home/tom/.leo/d:/test/jython/unicode/punct_jy.py
not found: /home/tom/.leo/d:/test/jython/unicode/unicode_fail.py

Looks like a two path portions are being incorrectly put together. Perhaps my recent discovery of Path Expressions will help:

The proper way is to use {{ and }} to specify the expression:

@path {{g.os_path_join(g.app.loadDir, '../../tools/webroot')}}

...

not found: '@auto testconfig.ini'
not found: '@auto readconfig.py


I've no insight here, but wouldn't be surprised if it's a knock on effect from the previous.

-matt

Viktor Ransmayr

unread,
Mar 22, 2020, 1:54:46 PM3/22/20
to leo-e...@googlegroups.com
Hello Matt,

Am So., 22. März 2020 um 18:28 Uhr schrieb Matt Wilkie <map...@gmail.com>:
Installation into a new PyVE on Debian went well - and - I did not notice any problems so far.

Good to hear Viktor. If I'm not mistaken this is the first trouble-free install in your environment for a number of releases. Yay :)


I've recently changed my environment at home, that's why I was reporting first for Leo inside a Debian-based VM.

Due to this new environment at home, it should be much easier to provide my F/B for Debian, Fedora as well as Windows in the near future.

With kind regards,

Viktor

Thomas Passin

unread,
Mar 22, 2020, 2:01:21 PM3/22/20
to leo-editor
It turns out that those were long-forgotten files in my workbook.leo outline.  They didn't even exist on-disk in my Linux VMs.

tfer

unread,
Mar 22, 2020, 7:11:32 PM3/22/20
to leo-editor
Thanks Matt, I was beginning to suspect there was something like these from some of the comments in setup.py, and ran across the "pip -e" variant on stack overflow.  I'm going to delete my leobase env and try this to see if it get rid of the error. 
Reply all
Reply to author
Forward
0 new messages