docs: Installing Leo from sources (all platforms)
143 views
Skip to first unread message
Matt Wilkie
Oct 10, 2019, 4:29:59 AM10/10/19
to leo-editor
I just pushed 51ca4f21b956beced0951de02a399e56a070ca01 which contains generic install-from-source instructions for all platforms. It might need some format tuning and perhaps other edting. I think it could replace or be merged with a couple of the following nodes. Or at least something to improve the flow and reduce redundancy. Have at 'er. ;-)
.../leo-editor/leo/doc/LeoDocs.leo#Leo's Documentation-->Installing & running Leo-->@rst html/installing.html-->Installing Leo itself-->Installing Leo from sources (all platforms)
QQQ
Generic recipe for all platforms. Adjustment for local norms is expected. For example `7z` could be `unzip` or interactive extraction and `wget` could be a browser download.
Linux: it's generally advised to use pip ``--user`` flag instead of `sudo`.
Assumes **Python 3.6+** is installed and in PATH.
Installing from source code into a new environment must be done in discrete steps: **download**, **unpack archive**, and **install as editable** mode.
Example::
wget https://github.com/leo-editor/leo-editor/archive/devel.zip
7z x devel.zip -o C:\apps
pip install --editable C:\apps\leo-editor-devel
For easier upgrading substitute ``git clone`` for wget & 7z steps::
git clone --single-branch -b devel --depth=200 https://github.com/leo-editor/leo-editor.git
pip install --editable leo-editor
time passes, upgrade desired::
pushd c:\apps\leo-editor
git pull
pip uninstall leo
pip install --editable .
`single-branch`, `b` and `depth` are all optional, but will dramatically speed up download time as it only grabs the latest development branch and skips all but the last couple weeks or months of history.
###
Note
###
Direct ``pip install https://github.com/leo-editor/leo-editor/archive/devel.zip`` does *not* work. For proper operation Leo relies on presence of certain files outside of the standard Python `site-packages` folder structure.
See `Running Leo`_ for how to run Leo after installing it.
Linux: it's generally advised to use pip ``--user`` flag instead of `sudo`.
Assumes **Python 3.6+** is installed and in PATH.
Installing from source code into a new environment must be done in discrete steps: **download**, **unpack archive**, and **install as editable** mode.
Example::
wget https://github.com/leo-editor/leo-editor/archive/devel.zip
7z x devel.zip -o C:\apps
pip install --editable C:\apps\leo-editor-devel
For easier upgrading substitute ``git clone`` for wget & 7z steps::
git clone --single-branch -b devel --depth=200 https://github.com/leo-editor/leo-editor.git
pip install --editable leo-editor
time passes, upgrade desired::
pushd c:\apps\leo-editor
git pull
pip uninstall leo
pip install --editable .
`single-branch`, `b` and `depth` are all optional, but will dramatically speed up download time as it only grabs the latest development branch and skips all but the last couple weeks or months of history.
###
Note
###
Direct ``pip install https://github.com/leo-editor/leo-editor/archive/devel.zip`` does *not* work. For proper operation Leo relies on presence of certain files outside of the standard Python `site-packages` folder structure.
See `Running Leo`_ for how to run Leo after installing it.
QQQ
-matt
Edward K. Ream
Oct 10, 2019, 9:19:54 AM10/10/19
to leo-editor
On Thu, Oct 10, 2019 at 3:30 AM Matt Wilkie <map...@gmail.com> wrote:
I just pushed 51ca4f21b956beced0951de02a399e56a070ca01 which contains generic install-from-source instructions for all platforms. It might need some format tuning and perhaps other editing. I think it could replace or be merged with a couple of the following nodes. Or at least something to improve the flow and reduce redundancy. Have at 'er. ;-)
.../leo-editor/leo/doc/LeoDocs.leo#Leo's Documentation-->Installing & running Leo-->@rst html/installing.html-->Installing Leo itself-->Installing Leo from sources (all platforms)QQQGeneric recipe for all platforms. Adjustment for local norms is expected.
[snip]
Many thanks for this work. Nobody knows better than I how picky these instructions are.
Edward
Viktor Ransmayr
Oct 12, 2019, 8:10:24 AM10/12/19
to leo-e...@googlegroups.com
Hello Matt, hello Edward,
Am Do., 10. Okt. 2019 um 10:30 Uhr schrieb Matt Wilkie <map...@gmail.com>:
I just pushed 51ca4f21b956beced0951de02a399e56a070ca01 which contains generic install-from-source instructions for all platforms. It might need some format tuning and perhaps other edting. I think it could replace or be merged with a couple of the following nodes. Or at least something to improve the flow and reduce redundancy. Have at 'er. ;-)
@Matt: Thanks for this. - I'll provide my feedback in the context of my attempt to install a version of the Leo Developement Branch in a new Python Virtual Environment (PyVE) without the need to use git as a Leo Newbie / Non Leo Developer ...
Direct ``pip install https://github.com/leo-editor/leo-editor/archive/devel.zip`` does *not* work. For proper operation Leo relies on presence of certain files outside of the standard Python `site-packages` folder structure.
@Edward: Has been a deliberate design decision of your side & if yes, please explain why?
With kind regards,
Viktor
Viktor Ransmayr
Oct 12, 2019, 8:14:44 AM10/12/19
to leo-e...@googlegroups.com
Hello Edward,
Am Samstag, 12. Oktober 2019 14:10:24 UTC+2 schrieb Viktor Ransmayr:
...
Direct ``pip install https://github.com/leo-editor/leo-editor/archive/devel.zip`` does *not* work. For proper operation Leo relies on presence of certain files outside of the standard Python `site-packages` folder structure.@Edward: Has been a deliberate design decision of your side & if yes, please explain why?
The question should read: Has this been a deliberate design decision on your side & if yes, please explain why?
Viktor
Viktor Ransmayr
Oct 12, 2019, 9:43:05 AM10/12/19
to leo-e...@googlegroups.com
Hello Matt,
Am Samstag, 12. Oktober 2019 14:10:24 UTC+2 schrieb Viktor Ransmayr:
Hello Matt, hello Edward,Am Do., 10. Okt. 2019 um 10:30 Uhr schrieb Matt Wilkie <map...@gmail.com>:I just pushed 51ca4f21b956beced0951de02a399e56a070ca01 which contains generic install-from-source instructions for all platforms. It might need some format tuning and perhaps other edting. I think it could replace or be merged with a couple of the following nodes. Or at least something to improve the flow and reduce redundancy. Have at 'er. ;-)@Matt: Thanks for this. - I'll provide my feedback in the context of my attempt to install a version of the Leo Developement Branch in a new Python Virtual Environment (PyVE) without the need to use git as a Leo Newbie / Non Leo Developer ...
Here's an **intermediate** status report, which show very nicely how difficult it is to create correct & precise documentation.
TL;DR : I ran into unforseen problems, since I don't use theWindows Command Prompt but use PowerShell as my default console in Windows.
Longer version of the story:
I tried to follow your instructions as closely as possible:
::
::
Assumes **Python 3.6+** is installed and in PATH.
Installing from source code into a new environment must be done in discrete steps: **download**, **unpack archive**, and **install as editable** mode.
Example::
wget https://github.com/leo-editor/leo-editor/archive/devel.zip
7z x devel.zip -o C:\apps
pip install --editable C:\apps\leo-editor-devel
Here are the steps that I performed:
1) Create & activate a new PyVE. - OK. - See "Log-001"
2) Download & install wget. - Not OK. - See "Log-002"
3) It looks like you don't even have to install 'wget' if you are a PS user. - Partially OK. - See "Log-003"
1) Create & activate a new PyVE. - OK. - See "Log-001"
2) Download & install wget. - Not OK. - See "Log-002"
3) It looks like you don't even have to install 'wget' if you are a PS user. - Partially OK. - See "Log-003"
I'll only publish Log-002 & Log-003 here, since they contain the interesting content ...
Now I'll continue to try to get a version of the Leo Developement Branch in a new Python Virtual Environment (PyVE) working without the need to use git as a Leo User ...
With kind regards,
Viktor
###
<Log-002>
Install 'wget' as administrator ...
* Accept compliance with GPL version 3
* Install into C:/Program Files (x86)/GnuWin32/
* Keep seleceted components ...
* Chose not to create a Start Menu folder ...
* De-select all additional tasks ...
* Installation did succeed ...
* Verify availability of 'wget' in the PyVE - No OK. - See below:
::
Windows PowerShell
Copyright (C) Microsoft Corporation. Alle Rechte vorbehalten.
Lernen Sie das neue plattformübergreifende PowerShell kennen – https://aka.ms/pscore6
PS C:\Users\Viktor> cd pyve/github/leo-devel
PS C:\Users\Viktor\pyve\github\leo-devel> wget --version
wget : Der Remotename konnte nicht aufgelöst werden: '--version'
In Zeile:1 Zeichen:1
+ wget --version
+ ~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-WebRequest], WebException
+ FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand
PS C:\Users\Viktor\pyve\github\leo-devel>
* Accept compliance with GPL version 3
* Install into C:/Program Files (x86)/GnuWin32/
* Keep seleceted components ...
* Chose not to create a Start Menu folder ...
* De-select all additional tasks ...
* Installation did succeed ...
* Verify availability of 'wget' in the PyVE - No OK. - See below:
::
Windows PowerShell
Copyright (C) Microsoft Corporation. Alle Rechte vorbehalten.
Lernen Sie das neue plattformübergreifende PowerShell kennen – https://aka.ms/pscore6
PS C:\Users\Viktor> cd pyve/github/leo-devel
PS C:\Users\Viktor\pyve\github\leo-devel> wget --version
wget : Der Remotename konnte nicht aufgelöst werden: '--version'
In Zeile:1 Zeichen:1
+ wget --version
+ ~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-WebRequest], WebException
+ FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand
PS C:\Users\Viktor\pyve\github\leo-devel>
</Log-002>
<Log-003>
PS C:\Users\Viktor\pyve\github\leo-devel> wget
Cmdlet Invoke-WebRequest an der Befehlspipelineposition 1
Geben Sie Werte für die folgenden Parameter an:
Uri: https://github.com/leo-editor/leo-editor/archive/devel.zip
StatusCode : 200
StatusDescription : OK
Content : {80, 75, 3, 4...}
RawContent : HTTP/1.1 200 OK
Transfer-Encoding: chunked
Access-Control-Allow-Origin: https://render.githubusercontent.com
Content-Security-Policy: default-src 'none'; style-src 'unsafe-inline'; sandbox
Strict-...
Headers : {[Transfer-Encoding, chunked], [Access-Control-Allow-Origin,
https://render.githubusercontent.com], [Content-Security-Policy, default-src 'none'; style-src
'unsafe-inline'; sandbox], [Strict-Transport-Security, max-age=31536000]...}
RawContentLength : 11727380
PS C:\Users\Viktor\pyve\github\leo-devel> ls
Verzeichnis: C:\Users\Viktor\pyve\github\leo-devel
Mode LastWriteTime Length Name
---- ------------- ------ ----
d----- 12.10.2019 14:30 Include
d----- 12.10.2019 14:30 Lib
d----- 12.10.2019 14:30 Scripts
-a---- 12.10.2019 14:30 85 pyvenv.cfg
PS C:\Users\Viktor\pyve\github\leo-devel>
###
It is unclear where to 'devel.zip' got copied to? - Investigate ...
Cmdlet Invoke-WebRequest an der Befehlspipelineposition 1
Geben Sie Werte für die folgenden Parameter an:
Uri: https://github.com/leo-editor/leo-editor/archive/devel.zip
StatusCode : 200
StatusDescription : OK
Content : {80, 75, 3, 4...}
RawContent : HTTP/1.1 200 OK
Transfer-Encoding: chunked
Access-Control-Allow-Origin: https://render.githubusercontent.com
Content-Security-Policy: default-src 'none'; style-src 'unsafe-inline'; sandbox
Strict-...
Headers : {[Transfer-Encoding, chunked], [Access-Control-Allow-Origin,
https://render.githubusercontent.com], [Content-Security-Policy, default-src 'none'; style-src
'unsafe-inline'; sandbox], [Strict-Transport-Security, max-age=31536000]...}
RawContentLength : 11727380
PS C:\Users\Viktor\pyve\github\leo-devel> ls
Verzeichnis: C:\Users\Viktor\pyve\github\leo-devel
Mode LastWriteTime Length Name
---- ------------- ------ ----
d----- 12.10.2019 14:30 Include
d----- 12.10.2019 14:30 Lib
d----- 12.10.2019 14:30 Scripts
-a---- 12.10.2019 14:30 85 pyvenv.cfg
PS C:\Users\Viktor\pyve\github\leo-devel>
###
It is unclear where to 'devel.zip' got copied to? - Investigate ...
</Log-003>
Viktor Ransmayr
Oct 12, 2019, 11:10:17 AM10/12/19
to leo-e...@googlegroups.com
Hello Matt,
Am Sa., 12. Okt. 2019 um 15:43 Uhr schrieb Viktor Ransmayr <viktor....@gmail.com>:
Hello Matt,
Am Samstag, 12. Oktober 2019 14:10:24 UTC+2 schrieb Viktor Ransmayr:Am Do., 10. Okt. 2019 um 10:30 Uhr schrieb Matt Wilkie <map...@gmail.com>:I just pushed 51ca4f21b956beced0951de02a399e56a070ca01 which contains generic install-from-source instructions for all platforms. It might need some format tuning and perhaps other edting. I think it could replace or be merged with a couple of the following nodes. Or at least something to improve the flow and reduce redundancy. Have at 'er. ;-)@Matt: Thanks for this. - I'll provide my feedback in the context of my attempt to install a version of the Leo Developement Branch in a new Python Virtual Environment (PyVE) without the need to use git as a Leo Newbie / Non Leo Developer ...Here's an **intermediate** status report, which show very nicely how difficult it is to create correct & precise documentation.TL;DR : I ran into unforseen problems, since I don't use theWindows Command Prompt but use PowerShell as my default console in Windows.
Here's a follow-up status report, which shows the limited progress I made:
- Use 'wget' alias w/i PS. - OK. - See "Log-004"
- Use 'extract-archive' w/i PS. - OK. - See "Log-005"
- Use 'pip' w/i PS. - Not OK. - See "Log-006"
Do you have an explanation, why pip fails in this context?
For the moment I'll stop here - and - restart my activities concerning the usage of a 'usable' dark theme in a/ my Windows 10 environment.
With kind regards,
Viktor
###
<Log-004>
PS C:\Users\Viktor\pyve\github\leo-devel> wget -OutFile ./devel.zip https://github.com/leo-editor/leo-editor/archive/devel.zip PS C:\Users\Viktor\pyve\github\leo-devel> ls
Verzeichnis: C:\Users\Viktor\pyve\github\leo-devel
Mode LastWriteTime Length Name
---- ------------- ------ ----
d----- 12.10.2019 14:30 Include
d----- 12.10.2019 14:30 Lib
d----- 12.10.2019 14:30 Scripts
-a---- 12.10.2019 16:41 11727380 devel.zip
-a---- 12.10.2019 14:30 85 pyvenv.cfg
PS C:\Users\Viktor\pyve\github\leo-devel>
</Log-004>
<Log-005>
PS C:\Users\Viktor\pyve\github\leo-devel> expand-archive ./devel.zip PS C:\Users\Viktor\pyve\github\leo-devel> ls
Verzeichnis: C:\Users\Viktor\pyve\github\leo-devel
Mode LastWriteTime Length Name
---- ------------- ------ ----
d----- 12.10.2019 16:48 devel
d----- 12.10.2019 14:30 Include
d----- 12.10.2019 14:30 Lib
d----- 12.10.2019 14:30 Scripts
-a---- 12.10.2019 16:41 11727380 devel.zip
-a---- 12.10.2019 14:30 85 pyvenv.cfg
PS C:\Users\Viktor\pyve\github\leo-devel>
</Log-005>
<Log-006>
PS C:\Users\Viktor\pyve\github\leo-devel> pip install --editable ./devel
ERROR: File "setup.py" not found. Directory cannot be installed in editable mode: C:\Users\Viktor\pyve\github\leo-devel\devel
ERROR: File "setup.py" not found. Directory cannot be installed in editable mode: C:\Users\Viktor\pyve\github\leo-devel\devel
PS C:\Users\Viktor\pyve\github\leo-devel>
</Log-006>
Viktor Ransmayr
Oct 12, 2019, 11:45:19 AM10/12/19
to leo-editor
Hello Matt,
Am Samstag, 12. Oktober 2019 17:10:17 UTC+2 schrieb Viktor Ransmayr:
Am Sa., 12. Okt. 2019 um 15:43 Uhr schrieb Viktor Ransmayr <viktor....@gmail.com>:Am Samstag, 12. Oktober 2019 14:10:24 UTC+2 schrieb Viktor Ransmayr:Am Do., 10. Okt. 2019 um 10:30 Uhr schrieb Matt Wilkie <map...@gmail.com>:I just pushed 51ca4f21b956beced0951de02a399e56a070ca01 which contains generic install-from-source instructions for all platforms. It might need some format tuning and perhaps other edting. I think it could replace or be merged with a couple of the following nodes. Or at least something to improve the flow and reduce redundancy. Have at 'er. ;-)@Matt: Thanks for this. - I'll provide my feedback in the context of my attempt to install a version of the Leo Developement Branch in a new Python Virtual Environment (PyVE) without the need to use git as a Leo Newbie / Non Leo Developer ...Here's an **intermediate** status report, which show very nicely how difficult it is to create correct & precise documentation.TL;DR : I ran into unforseen problems, since I don't use theWindows Command Prompt but use PowerShell as my default console in Windows.Here's a follow-up status report, which shows the limited progress I made:
- Use 'wget' alias w/i PS. - OK. - See "Log-004"
- Use 'extract-archive' w/i PS. - OK. - See "Log-005"
- Use 'pip' w/i PS. - Not OK. - See "Log-006"
Do you have an explanation, why pip fails in this context?
Please ignore my question! - The problem was in front of the terminal ;-)
With kind regards,
Viktor
PS: I'll report back, when I have the complete process properly documented ...
Matt Wilkie
Oct 12, 2019, 1:17:50 PM10/12/19
to leo-editor
Direct ``pip install https://github.com/leo-editor/leo-editor/archive/devel.zip`` does *not* work. For proper operation Leo relies on presence of certain files outside of the standard Python `site-packages` folder structure.@Edward: Has been a deliberate design decision of your side & if yes, please explain why?The question should read: Has this been a deliberate design decision on your side & if yes, please explain why?
No, not deliberate. It's a result from Python's package evolution and how pip works.
Leo is both a Library and an Application and python packaging is designed mostly around the Library part. We could make it work and there are a couple good reasons aside from unwanted pip results to do it, but it is a major effort that would make every developer who uses Leo have to adjust their workflow and tooling. The source code tree structure would change at root, breaking many many scripts. Not gonna happen anytime soon. ;-)
-matt
Matt Wilkie
Oct 12, 2019, 2:39:08 PM10/12/19
to leo-editor
PS C:\Users\Viktor\pyve\github\leo-devel> pip install --editable ./devel
ERROR: File "setup.py" not found. Directory cannot be installed in editable mode: C:\Users\Viktor\pyve\github\leo-devel\devel
1 dir too deep. The path needs to be to folder that contains setup.py.
-matt
Edward K. Ream
Oct 12, 2019, 6:15:43 PM10/12/19
to leo-editor
On Sat, Oct 12, 2019 at 7:10 AM Viktor Ransmayr <viktor....@gmail.com> wrote:
@Edward: Has been a deliberate design decision of your side & if yes, please explain why?
I'm delegating all choices to Matt.
Edward
Viktor Ransmayr
Oct 13, 2019, 3:42:11 PM10/13/19
to leo-e...@googlegroups.com
Hello Matt,
Am Samstag, 12. Oktober 2019 15:43:05 UTC+2 schrieb Viktor Ransmayr:
Am Samstag, 12. Oktober 2019 14:10:24 UTC+2 schrieb Viktor Ransmayr:Am Do., 10. Okt. 2019 um 10:30 Uhr schrieb Matt Wilkie <map...@gmail.com>:I just pushed 51ca4f21b956beced0951de02a399e56a070ca01 which contains generic install-from-source instructions for all platforms. It might need some format tuning and perhaps other edting. I think it could replace or be merged with a couple of the following nodes. Or at least something to improve the flow and reduce redundancy. Have at 'er. ;-)@Matt: Thanks for this. - I'll provide my feedback in the context of my attempt to install a version of the Leo Developement Branch in a new Python Virtual Environment (PyVE) without the need to use git as a Leo Newbie / Non Leo Developer ...Here's an **intermediate** status report, which show very nicely how difficult it is to create correct & precise documentation.TL;DR : I ran into unforseen problems, since I don't use theWindows Command Prompt but use PowerShell as my default console in Windows.Longer version of the story:I tried to follow your instructions as closely as possible:
::
Assumes **Python 3.6+** is installed and in PATH.
Installing from source code into a new environment must be done in discrete steps: **download**, **unpack archive**, and **install as editable** mode.
Example::
wget https://github.com/leo-editor/leo-editor/archive/devel.zip
7z x devel.zip -o C:\apps
pip install --editable C:\apps\leo-editor-devel
I now adjusted my approach. - That is I tried to follow your instructions as closely as possible - but - took explicitely into account that I'm using Powershell 5 & Windows 10 & therefore do not need to use 'wget' and '7z' ...
Here are the steps that I used for my second attempt :
- Create & activate a new PyVE. - OK. - See "Log-001"
- Use 'Invoke-WebRequest' to download the current version of 'devel.zip' from GitHub. - OK. - See "Log-002"
- Use 'Expand-Archive' to extract the downloaded archive. - OK. - See "Log-003"
- Use 'pip' to install 'leo-devel'. - OK. - See "Log-004"
- Start 'leo-devel' - Not OK. - No further information available ...
- Close the 'leo-master' instance and retry to start 'leo-devel' using 'leo-m' ...
- Start 'leo-devel' again. - Not OK. - See "Log-005"
I'm just reporting the content of 'Log-005' here.
Now I really need your feedback on what the problem is ...
With kind regards,
Viktor
###
<Log-005>
(leo-devel) PS C:\Users\Viktor\pyve\github\leo-devel\devel> cd ..
(leo-devel) PS C:\Users\Viktor\pyve\github\leo-devel> leo-m
--global-docks: False
Leo 6.1-devel
leo_excepthook Uncaught Python exception: [WinError 3] Das System kann den angegebenen Pfad nicht finden: 'C:/users/viktor/pyve/ve4ileo/lib/site-packages/leo/doc/quickstart.leo'
NoneType: None
(leo-devel) PS C:\Users\Viktor\pyve\github\leo-devel>
(leo-devel) PS C:\Users\Viktor\pyve\github\leo-devel> leo-m
--global-docks: False
Leo 6.1-devel
leo_excepthook Uncaught Python exception: [WinError 3] Das System kann den angegebenen Pfad nicht finden: 'C:/users/viktor/pyve/ve4ileo/lib/site-packages/leo/doc/quickstart.leo'
NoneType: None
(leo-devel) PS C:\Users\Viktor\pyve\github\leo-devel>
</Log-005>
Matt Wilkie
Oct 13, 2019, 4:23:48 PM10/13/19
to leo-editor
Viktor does this work? (adjust to wherever launchLeo.py is):
python C:\Users\Viktor\pyve\github\leo-devel\launchLeo.pyPfad nicht finden: 'C:/users/viktor/pyve/ve4ileo/lib/site-packages/leo/doc/quickstart.leo'
[...]
(leo-devel) PS C:\Users\Viktor\pyve\github\leo-devel>
The root of these paths don't match which indicates the VE is not clean, that there is a prior install of Leo in the mix. Leo should be looking for quickstart.leo under `github\leo-devel`
I would try:
(A) `pip unininstall leo`, inspect `PYTHONHOME\lib\site-packages` and `PYTHONHOME\Scripts` for anything Leo, and delete them if found. Then try `pip install --editable ...` again.
Or: (B) Start from the top with a new VE.
-matt
Viktor Ransmayr
Oct 14, 2019, 1:51:20 AM10/14/19
to leo-editor
Hello Matt;
Viktor does this work? (adjust to wherever launchLeo.py is):
No. - See "Log-001"
[...]Pfad nicht finden: 'C:/users/viktor/pyve/ve4ileo/lib/site-packages/leo/doc/quickstart.leo'(leo-devel) PS C:\Users\Viktor\pyve\github\leo-devel>The root of these paths don't match which indicates the VE is not clean, that there is a prior install of Leo in the mix. Leo should be looking for quickstart.leo under `github\leo-devel`I would try:(A) `pip unininstall leo`, inspect `PYTHONHOME\lib\site-packages` and `PYTHONHOME\Scripts` for anything Leo, and delete them if found. Then try `pip install --editable ...` again.Or: (B) Start from the top with a new VE.
I'll try that tonight & report back.
With kind regards,
Viktor
###
<Log-001>
Windows PowerShell
Copyright (C) Microsoft Corporation. Alle Rechte vorbehalten.
Lernen Sie das neue plattformübergreifende PowerShell kennen – https://aka.ms/pscore6
Copyright (C) Microsoft Corporation. Alle Rechte vorbehalten.
Lernen Sie das neue plattformübergreifende PowerShell kennen – https://aka.ms/pscore6
PS C:\Users\Viktor> cd pyve/github/leo-devel*
PS C:\Users\Viktor\pyve\github\leo-devel> ls
PS C:\Users\Viktor\pyve\github\leo-devel> ls
Verzeichnis: C:\Users\Viktor\pyve\github\leo-devel
Mode LastWriteTime Length Name
---- ------------- ------ ----
d----- 13.10.2019 21:02 devel
d----- 13.10.2019 20:42 Include
d----- 13.10.2019 20:42 Lib
d----- 13.10.2019 21:15 Scripts
-a---- 13.10.2019 20:58 11728069 devel.zip
-a---- 13.10.2019 20:42 76 pyvenv.cfg
PS C:\Users\Viktor\pyve\github\leo-devel> cd devel
PS C:\Users\Viktor\pyve\github\leo-devel\devel> cd leo-editor-devel
PS C:\Users\Viktor\pyve\github\leo-devel\devel\leo-editor-devel> python ./launchLeo.py
--global-docks: False
import-jupyter-notebook requires nbformat package
Can not Import Qt
PS C:\Users\Viktor\pyve\github\leo-devel\devel\leo-editor-devel>
d----- 13.10.2019 20:42 Include
d----- 13.10.2019 20:42 Lib
d----- 13.10.2019 21:15 Scripts
-a---- 13.10.2019 20:58 11728069 devel.zip
-a---- 13.10.2019 20:42 76 pyvenv.cfg
PS C:\Users\Viktor\pyve\github\leo-devel> cd devel
PS C:\Users\Viktor\pyve\github\leo-devel\devel> cd leo-editor-devel
PS C:\Users\Viktor\pyve\github\leo-devel\devel\leo-editor-devel> python ./launchLeo.py
--global-docks: False
import-jupyter-notebook requires nbformat package
Can not Import Qt
PS C:\Users\Viktor\pyve\github\leo-devel\devel\leo-editor-devel>
</Log-001>
Edward K. Ream
Oct 14, 2019, 2:54:59 AM10/14/19
to leo-editor
On Mon, Oct 14, 2019 at 12:51 AM Viktor Ransmayr <viktor....@gmail.com> wrote:
Viktor, Matt,
Please take this discussion offline, and summarize your results on leo-editor when you have resolved this.
Edward
Matt Wilkie
Oct 14, 2019, 9:35:28 PM10/14/19
to leo-editor
Please take this discussion offline, and summarize your results on leo-editor when you have resolved this.
Yeah, this is pretty noisy.
-matt
Viktor Ransmayr
Oct 19, 2019, 5:20:36 AM10/19/19
to leo-e...@googlegroups.com
Hello Edward,
Am Mo., 14. Okt. 2019 um 08:54 Uhr schrieb Edward K. Ream <edre...@gmail.com>:
Viktor, Matt,Please take this discussion offline, and summarize your results on leo-editor when you have resolved this.
I leave the technical details for Matt to explain - but - we now finally reached a state, where the underlying issue is clearly identified :-)
I can demonstrate, that such an installation works, if the "Leo-devel" instance starts w/o an existing '~/.leo' directory - and - on the other hand consistently fails, when my existing '~/.leo' directory is used.
Note: With the content in this directory I don't have any issues at all when using 'Leo-6.0-final' ...
With kind regards,
Viktor
Edward K. Ream
Oct 19, 2019, 10:02:15 AM10/19/19
to leo-editor
On Sat, Oct 19, 2019 at 4:20 AM Viktor Ransmayr <viktor....@gmail.com> wrote:
I leave the technical details for Matt to explain - but - we now finally reached a state, where the underlying issue is clearly identified :-)I can demonstrate, that such an installation works, if the "Leo-devel" instance starts w/o an existing '~/.leo' directory - and - on the other hand consistently fails, when my existing '~/.leo' directory is used.
Well done, Viktor. Thanks for your persistence.
Edward
Matt Wilkie
Oct 20, 2019, 11:44:43 PM10/20/19
to leo-editor
I can demonstrate, that such an installation works, if the "Leo-devel" instance starts w/o an existing '~/.leo' directory - and - on the other hand consistently fails, when my existing '~/.leo' directory is used.Well done, Viktor. Thanks for your persistence.
Viktor's refusal to give up is indeed noteworthy. I would have given up long ago, and only persisted here myself because, well I wasn't going to stop if he wasn't!
-matt
Matt Wilkie
Oct 21, 2019, 12:23:32 AM10/21/19
to leo-editor
I leave the technical details for Matt to explain - but - we now finally reached a state, where the underlying issue is clearly identified :-)
https://github.com/leo-editor/leo-editor/issues/1415 - Leo crashes on startup with
unexpected exception loading session and then unexpected reading empty workbook
errors on startup. (I note an apparent missing word in 2nd message.)
Both tracebacks complain that a .leo file doesn't exist. It doesn't,
said file is in an old directory that doesn't exist anymore. After removing HOME\.leo folder Leo starts okay. Putting the problem .leo folder back is a reliable way of reproducing the crash.-matt
Reply all
Reply to author
Forward
0 new messages