Leo 6.7.8.post1 is ready for testing

[Edward K. Ream]

You can now install Leo 6.7.8.post1 from pypi. This "post" release changes only distribution-related files. See PR #3835 for the details.

The "post1" prefix is required to meet the more stringent pypi naming conventions.

Please test the installation process immediately and report your experience.

I'll announce Leo 6.7.8 widely when you all give the all-clear :-)

Edward

[Thomas Passin]

python3 -m pip install --user --upgrade leo==6.7.8.post1 succeeded on Linux Debian, although I had to install libxcb-cursor0 afterwards, as we've been seeing on some other distros.  After the install:

Leo 6.7.8.post1
Python 3.9.2, PyQt version 6.6.2
linux

[Thomas Passin]

Installed OK on Ubuntu 22.04, Python 3.10.

[Thomas Passin]

On Linux systems that don't allow installing user packages with pip because the system python is managed by the system, you can force installation using the --break-system packages option, like this:

python3 -m pip install --user --upgrade --break-system-packages leo==6.7.8.post1

You will know if this applies to you because you will have seen a message that starts like this:

error: externally-managed-environment

This environment is externally managed

╰─> To install Python packages system-wide, try apt install python3-xyz, where xyz is the package you are trying to install.

If you wish to install a non-Debian-packaged Python package, create a virtual environment using python3 -m venv path/to/venv. Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make sure you have python3-full installed.

The risk of actually over-riding a system package with the wrong version is probably minimal since Leo doesn't seem to use packages in the system directories.

If you already are using a venv for Leo, then there should be no problem with the install.

[Viktor Ransmayr]

Hello Edward,

Edward K. Ream schrieb am Dienstag, 19. März 2024 um 22:39:27 UTC+1:

You can now install Leo 6.7.8.post1 from pypi. This "post" release changes only distribution-related files. See PR #3835 for the details.

The "post1" prefix is required to meet the more stringent pypi naming conventions.

Please test the installation process immediately and report your experience.

 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 ...

After I installed Leo 6.7.8.post1 I gathered the following additional info, which might help:

[user@Test-VM2 ~]$
[user@Test-VM2 ~]$ python --version
Python 3.11.8
[user@Test-VM2 ~]$
[user@Test-VM2 ~]$ pip --version
pip 22.3.1 from /usr/lib/python3.11/site-packages/pip (python 3.11)
[user@Test-VM2 ~]$
[user@Test-VM2 ~]$ pip list  | grep leo
leo                           6.7.8.post1
[user@Test-VM2 ~]$
[user@Test-VM2 ~]$ which leo
/usr/bin/which: no leo in (/home/user/.local/bin:/home/user/bin:/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin)
[user@Test-VM2 ~]$

Please let me know if you need any further info about my environment.

With kind regards,

Viktor

[Edward K. Ream]

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

[Thomas Passin]

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.