Leo 6.6.4 will be the last release that supports python versions less than 3.9

[Edward K. Ream]

It's time to pull the plugin on ancient Python releases:

- Leo's support for Python 3.6, 3.7, and 3.8 is limited and buggy.

- Support for Python 3.6 is hindering full annotations.

- Earlier Python releases are now security risks.

- Binary installer exist for Windows, Ubuntu and MacOs.

  Just now it took me about 5 minutes to install Python 3.10 on Ubuntu.

Edward

[tbp1...@gmail.com]

I'm seeing the following error messages in the console today, after updating devel from GitHub:

file not found: C:/Users/tom/AppData/Roaming/Python/Python310/site-packages/.mypy.ini
file not found: C:/Users/tom/AppData/Roaming/Python/Python310/site-packages/launchLeo.py
can not open C:/Users/tom/AppData/Roaming/Python/Python310/site-packages/leo_to_html.xsl
can not open C:/Users/tom/AppData/Roaming/Python/Python310/site-packages/run_pytest_tests.py
can not open C:/Users/tom/AppData/Roaming/Python/Python310/site-packages/run_travis_unit_tests.py

Those files do not exist in C:/Users/tom/AppData/Roaming/Python/Python310/site-packages/, and they don't seem like the kind of files that ought to be there.  My Leo directory tree is actually in C:\Tom\git\leo-editor. So Leo is looking in the wrong location.

Version info:

Leo 6.6.3
Python 3.10.4, PyQt version 5.15.2
Windows 10 AMD64 (build 10.0.19043) SP0

Also, I notice that the usual branch/build items are not included in the version info, which they used to be.

[Edward K. Ream]

On Wed, Aug 31, 2022 at 10:30 PM tbp1...@gmail.com <tbp1...@gmail.com> wrote:

I'm seeing the following error messages in the console today, after updating devel from GitHub:

Hmm. Not sure why you are having problems. I just did the following as a test:

git clone https://github.com/leo-editor/leo-editor.git leo-editor-test

cd leo-editor-test

python launchLeo.py

All seems well.  I suggest you reinstall Leo using git clone into a new leo-editor folder:

git clone https://github.com/leo-editor/leo-editor.git

Edward

[tbp1...@gmail.com]

Funny, I just launched another session and got the branch/changeset numbers.  I still get those wrong file paths, though.  I start Leo with python3 -m leo.core.runLeo.

[tbp1...@gmail.com]

The mystery is solved and all is well (no error messages).  Turns out I accidentally started my main Leo session from the Python install library instead of from my git clone.  Then I opened LeoPyRef.leo.  It was open when I closed Leo, so the next time I started Leo - from the git clone as intended - it re-opened all the previously open outlines.  Except that the open LeoPyRef outline was still the one from the Python install tree, not the git clone.  But of course, since I had opened the clone, I expected the outline to be the one in the clone tree.  Talk about cognitive dissonance!

It took way too long for me to notice that the wrong outline was getting opened on every launch.  I could have found out from the title bar of Leo's window, but how often do you actually read that?

[Edward K. Ream]

On Thu, Sep 1, 2022 at 6:11 AM tbp1...@gmail.com <tbp1...@gmail.com> wrote:

The mystery is solved and all is well (no error messages). 

Thanks for the update. I'll rest a bit easier now :-)

Edward