Aha! I didn't pick up on that because I always start Leo with python3 -m
leo.core.runLeo. I do that instead of using a script fromt the Scripts
directory because I don't let a new install of Python add those directories
to the path. And I do *that* because I used to need the Python 2.7 Script
directories on the path for reasons we don't need to get into. Also I have
many versions of Python on my machine and the scripts would only work for
one of them at a time anyway. I can launch Leo with any Python version I
want in the above incantation and it's become automatic.
On Wednesday, March 20, 2024 at 8:13:56 AM UTC-4 Edward K. Ream wrote:
> On Wednesday, March 20, 2024 at 3:13:41 AM UTC-5 Viktor wrote:
>
> I installed Leo 6.7.8.post1 into an existing 'venv' on a Fedora 38 VM -
> but - I could NOT run it using the 'leo' cmd from the shell.
>
> I also tried installing Leo 6.7.8.post1 into a completely new Fedora 38 VM
> w/o using a 'venv' - Same behaviour ...
>
>
> Thanks for your testing! It looks like a post2 release is called for.
>
> The old setup.py contained:
>
> entry_points = {
> 'console_scripts': [
> 'leo-c = leo.core.runLeo:run_console',
> 'leo-console = leo.core.runLeo:run_console',
> ],
> 'gui_scripts': ['leo = leo.core.runLeo:run'],
> }
>
> but pyproject.toml does not contain anything similar.
>
> *Leo's signon*
>
> The post2 release revert Leo's signon to 6.7.8, *not* 6.7.8.post2.
>
> Why? Because "post" releases should *only* fix release-related code,
> *never* real bugs.
>
> Edward
>
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/leo-editor/fda22629-2f6d-4587-bed7-cd88d996a98an%40googlegroups.com.
