Leo 6.7.3 released!

Edward K. Ream

unread,

May 12, 2023, 9:02:00 AM5/12/23

to leo-editor

Leo 6.7.3 is now available on GitHub and pypi. Many thanks to all those who have contributed to this release.

This release contains an important security fix. I recommend upgrading to Leo 6.7.3 unless you use the latest code in Leo's devel branch.

I'll delay announcing 6.7.3 publicly for a few days to give us all time to test the final release.

Edward

Edward K. Ream

unread,

May 12, 2023, 9:37:53 AM5/12/23

to leo-editor

On Friday, May 12, 2023 at 8:02:00 AM UTC-5 Edward K. Ream wrote:

Leo 6.7.3 is now available on GitHub and pypi. Many thanks to all those who have contributed to this release.

mypy rightly issues some complaints about master. I have verified that those complaints do not cause problems in the affected code, so I see no reason to change the release.

I have already fixed those complaints in devel.

Edward

Edward K. Ream

unread,

May 12, 2023, 10:02:18 AM5/12/23

to leo-editor

On Friday, May 12, 2023 at 8:37:53 AM UTC-5 Edward K. Ream wrote:

mypy rightly issues some complaints about master. I have verified that those complaints do not cause problems in the affected code, so I see no reason to change the release.

I have already fixed those complaints in devel.

PR #3331 removes no-longer used kwargs from calls g.es_exception and g.callers. Master should work properly because:

- g.es_exception has *args and **kwargs arguments.

- The incorrect calls to g.callers occur only in disabled trace statements in cursesGui2.py.

Edward

Félix

unread,

May 12, 2023, 3:20:07 PM5/12/23

to leo-editor

Next leoInteg (1.0.14) release will ask for minimum Leo version 6.7.3 :)

(coming "soon" this spring, before leojs beta 0.1)

Félix

Edward K. Ream

unread,

May 12, 2023, 3:24:20 PM5/12/23

to leo-e...@googlegroups.com

On Fri, May 12, 2023 at 2:20 PM Félix <felix...@gmail.com> wrote:

Next leoInteg (1.0.14) release will ask for minimum Leo version 6.7.3 :)
(coming "soon" this spring, before leojs beta 0.1)

Sounds good. Keep up your great work :-)

I'm a bit concerned about the problem with mypy complaints. The warnings themselves don't matter, but I wonder whether merging devel into master and back again may have created other problems.