Why is Script 'leo-m.exe' not available in Leo 6.1-final on PyPI?

[Viktor Ransmayr]

Hello Matt,

I've asked this question already earlier - but - I assume it got overlooked [1 & 2].

Why is the script 'leo-m.exe' available in the development-/ beta version of Leo (e.g. 6.1-b1-devel) but not in the master-/ final version of Leo (e.g. 6.1-final) at PyPI?

I just double-checked - and - the reported behaviour is still true for "Leo 6.2-b1-devel" as well ...

I think this script should be there at all times, since it is really helpful when something goes wrong unexpectedly.

With kind regards,

Viktor

---

[1] https://groups.google.com/d/msg/leo-editor/jVOoVzKv4no/bKTTmWWYAgAJ

[2] https://groups.google.com/d/msg/leo-editor/jVOoVzKv4no/rlIiCf8RAwAJ

[Matt Wilkie]

Why is the script 'leo-m.exe' available in the development-/ beta version of Leo (e.g. 6.1-b1-devel) but not in the master-/ final version of Leo (e.g. 6.1-final) at PyPI?

It's because master lags behind devel. It was inadvertently left out of the last master (final) release, and will be restored in next one.

 

I think this script should be there at all times, since it is really helpful when something goes wrong unexpectedly.

 

`python path\to\launchLeo.py` is the same as leo-messages.exe is always available, regardless of what does or doesn't happens with pip's install.

-matt

[Viktor Ransmayr]

Hello Matt,

Thanks for your explanation - but - the problem, as far as I can see, is that 'launchLeo.py' is missing, when installing Leo from PyPI ...

With kind regards,

Viktor

[Thomas Passin]

BTW, it's easier to run these modules using python -m, since you don't have to keep coming up with the full path.  That is:

python -m leo.core.runLeo # or launchLeo or whatever

Of course, the leo directory location has to be known to Python if it's not in the standard location (e.g., Lib/site-packages). 

[Viktor Ransmayr]

Hello Thomas,

Thanks for this reminder. - Yes, it does work for leo.core.runLeo - but - it does not work for launchLeo.py, since this file is not part of the Leo package when installed from PyPI.

AFAICT this is related to what Matt called "Leo's issue with (newer) Python Packaging Preferences" here [1].

With kind regards,

Viktor

---

[1] https://groups.google.com/d/msg/leo-editor/JxE7zwStAhA/03064iAhDgAJ

[Viktor Ransmayr]

Hello Matt,

Am Do., 26. Dez. 2019 um 20:49 Uhr schrieb Matt Wilkie <map...@gmail.com>:

Why is the script 'leo-m.exe' available in the development-/ beta version of Leo (e.g. 6.1-b1-devel) but not in the master-/ final version of Leo (e.g. 6.1-final) at PyPI?

It's because master lags behind devel. It was inadvertently left out of the last master (final) release, and will be restored in next one.

Do you plan to deliver that as part of Leo 6.1.1?

With kind regards,

Viktor

[Matt Wilkie]

BTW, it's easier to run these modules using python -m, since you don't have to keep coming up with the full path.  That is:

python -m leo.core.runLeo # or launchLeo or whatever

 

Of course, the leo directory location has to be known to Python if it's not in the standard location (e.g., Lib/site-packages). 

Excellent! I didn't know this. Thank you.

-matt

 

[Matt Wilkie]

Thanks for this reminder. - Yes, it does work for leo.core.runLeo - but - it does not work for launchLeo.py, since this file is not part of the Leo package when installed from PyPI.

AFAICT this is related to what Matt called "Leo's issue with (newer) Python Packaging Preferences" here [1].

[1] https://groups.google.com/d/msg/leo-editor/JxE7zwStAhA/03064iAhDgAJ

Yes, that's the right thread and info. Basically only things in the `./leo` folder tree are available when installing from PyPi, so non-from-source-code installs.

launchLeo.py is only needed when PYTHONHOME doesn't know about Leo, e.g. Leo hasn't been installed.

-matt

[Matt Wilkie]

Why is the script 'leo-m.exe' available in the development-/ beta version of Leo (e.g. 6.1-b1-devel) but not in the master-/ final version of Leo (e.g. 6.1-final) at PyPI?

It's because master lags behind devel. It was inadvertently left out of the last master (final) release, and will be restored in next one.

Do you plan to deliver that as part of Leo 6.1.1?

It will be in next release (https://github.com/leo-editor/leo-editor/releases), whatever number that is (sometimes numbers are skipped).

-matt