Summary of recent work

[Edward K. Ream]

This post summarizes a flurry of recently completed PRs. The PRs completed in the last week or so mostly relate to testing and distribution issues.  This post will be pre-writing for parts of the 6.8.10 documentation.

Recent changes should have minimal effect on most Leonistas.

A few script-related settings have changed (added, deleted), but these changes should be invisible even to programmers because of their defaults. I'll discuss settings in detail below.

Leo's core devs have a strong safety net.

Leo now supports a much faster (and safer) development environment:

- Strict GitHub tests run automatically on every commit. These checks run mypy and  `ruff check`.

- `ruff check` replaces flake8, pyflakes, and pylint, a huge increase in speed.

Leo's codebase also passes `ty leo`. The ty tool is a super-fast, super-strict type checker. It's beta quality, so the GitHub actions do not block if these checks fail. However, my local test script always runs `ty leo`.

Settings

`ruff check` supersedes flake8, pyflakes, and pylint, so the following settings are gone:

  @bool run-flake8-on-write
  @bool run-pyflakes-on-write
  @bool run-pylint-on-write

The equivalent new setting is:

  @bool run-ruff-on-write = False

The default is as shown, but I encourage devs to set this setting to True!

Summary

Leo 6.8.10 is a big step forward for Leo's core devs and other script writers.

Leonistas who don't write scripts or plugins should hardly notice any changes.

Many thanks to Ville for his tireless work over the last few days.

Leo's "devel" branch is nearly code complete. Please keep testing.

Edward

[Ville M. Vainio]

Correction: ty now puts ci red if it fails. We have zero ty errors now

--
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 leo-editor+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/leo-editor/34ad2a3a-760e-43d2-a2e8-c1d5f8033b59n%40googlegroups.com.

[Edward K. Ream]

On Sun, Aug 9, 2026 at 5:16 AM Ville M. Vainio <viva...@gmail.com> wrote:

Correction: ty now puts ci red if it fails. We have zero ty errors now

Excellent. Thanks for the correction.

Edward