Leo 6.7.8 released, but not to PyPi

[Edward K. Ream]

Leo https://leo-editor.github.io/leo-editor/ 6.7.8 is now available on GitHub but NOT on pypi. I have filed this twine issue.

I am enraged by the difficulties of creating a PyPi release. The point of this release was to simplify the installation of Leo, but that goal is on hold until I can update Leo on PyPi.

Any help you can give would be much appreciated.

I shall not announce Leo 6.7.8 until a PyPi release exists.

The highlights of Leo 6.7.8

This release simplifies Leo's install process.
See https://leo-editor.github.io/leo-editor/getting-started.html

• PR #3757: (leoTokens.py) Make Leo's beautifier 3x faster.
• PR #3771: Revert colorizing of f-strings.
• PR #3786: Support Nim.
• PR #3790: Add "get-unl" command to Leo's server.
• PR #3805: Fix problems with auto-completion and calltips.
• PR #3806: Fix problems with Leo's go-back and go-forward commands.
• PR #3807: Improve Leo's Python importer.
• PR #3817: Allow relative paths in gnx-based UNLs.
• The usual minor improvements and bug fixes.

Links

• Install Leo
• 6.7.8 Issues
• 6.7.8 Pull Requests
• Documentation
• Tutorials
• Video tutorials
• Forum
• Leo on GitHub
• LeoVue
• What people are saying about Leo
• A web page that displays .leo files
• More links

[Viktor Ransmayr]

Hello Edward,

Edward K. Ream schrieb am Freitag, 15. März 2024 um 11:08:11 UTC+1:

Leo https://leo-editor.github.io/leo-editor/ 6.7.8 is now available on GitHub but NOT on pypi. I have filed this twine issue.

I am enraged by the difficulties of creating a PyPi release. The point of this release was to simplify the installation of Leo, but that goal is on hold until I can update Leo on PyPi.

Any help you can give would be much appreciated.

 

Until Leo 6.7.7 (including) I was able to install & run Leo WITHOUT having to manually create a script on the Linux side. - This is no longer possible as of Leo 6.7.8 !

As I already explained in a separate message to Felix I'm trying to work with separate Python virtual environments (venv's) whenever possible ...

One for GitHub (devel branch), a second one for PyPI (released version) & a separate non-venv based one for LeoInteg. - Reason: see https://github.com/boltex/leointeg/issues/299

Here is initial 'path' & 'version' info about all three environments in a Debian 12 based VM:

### dedicated ~venv~ for GitHub:

user@debian-leo-study-vm:~$
user@debian-leo-study-vm:~$ cd PyVE/GitHub/Leo/
user@debian-leo-study-vm:~/PyVE/GitHub/Leo$
user@debian-leo-study-vm:~/PyVE/GitHub/Leo$ source bin/activate
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo$
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo$ which leo
/home/user/PyVE/GitHub/Leo/bin/leo
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo$
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo$ leo --version
Leo 6.7.7-devel, devel branch, build 401a78a10e
2023-12-31 12:42:43 -0600
Python 3.11.2
linux
(Leo) user@debian-leo-study-vm:~/PyVE/GitHub/Leo$

### dedicated ~venv~ for PyPI:

user@debian-leo-study-vm:~$
user@debian-leo-study-vm:~$ cd PyVE/PyPI/Leo/
user@debian-leo-study-vm:~/PyVE/PyPI/Leo$
user@debian-leo-study-vm:~/PyVE/PyPI/Leo$ source bin/activate
(Leo) user@debian-leo-study-vm:~/PyVE/PyPI/Leo$
(Leo) user@debian-leo-study-vm:~/PyVE/PyPI/Leo$ which leo
/home/user/PyVE/PyPI/Leo/bin/leo
(Leo) user@debian-leo-study-vm:~/PyVE/PyPI/Leo$
(Leo) user@debian-leo-study-vm:~/PyVE/PyPI/Leo$ leo --version
Leo 6.7.6
Python 3.11.2
linux
(Leo) user@debian-leo-study-vm:~/PyVE/PyPI/Leo$

### user-specific installation for LeoInteg:

user@debian-leo-study-vm:~$
user@debian-leo-study-vm:~$ which leo
/home/user/.local/bin/leo
user@debian-leo-study-vm:~$
user@debian-leo-study-vm:~$ leo --version
Leo 6.7.7
Python 3.11.2
linux
user@debian-leo-study-vm:~$

###

I believe it is somewhat related to the differences b/w Leo's source tree / directory content when installed from GitHub vs. PyPI.

I hope this provides at least some additional input for your analysis to resolve the issue ...

With kind regards,

Viktor

 

[Thomas Passin]

Then there's the brute force method - get the zip file from github, unzip it, and copy the leo directory into the user's site-packages directory.  To be thorough, one should delete the dist-info directory for Leo.  I don't know if venv would get this version when setting up a venv, though. Although it's not hard,  it isn't a wonderful procedure to ask a non-computer-savvy user to do.  It could probably be automated with a script, though.

[Edward K. Ream]

On Mon, Mar 18, 2024 at 8:42 AM Thomas Passin <tbp1...@gmail.com> wrote:

Then there's the brute force method - get the zip file from github, unzip it, and copy the leo directory into the user's site-packages directory. 

Thanks to you and Viktor for your comments. I'll be writing an Engineering Notebook post soon about the new challenges of creating a distro for PyPi.

Edward