Re: Leo 6.7.3 coming soon

[Edward K. Ream]

On Sunday, April 16, 2023 at 12:24:03 PM UTC-5 Edward K. Ream wrote:

Leo has 100% coverage of most of its core code. Full coverage doesn't 
guarantee correctness, but it's good enough.


Otoh, pydantic and hypothesis are worth investigating.  See #3280 
. This issue has no 
definite milestone. I would welcome help.

Edward

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/fa6f1b2b-41d8-4680-a9ba-8cd926a580e4n%40googlegroups.com.

Re: Leo 6.7.3 coming soon

[Edward K. Ream]

On Sun, Apr 16, 2023 at 7:57 AM David Szent-Györgyi 
wrote:

> If it is difficult for you, who know Leo's code base so well, to keep in
mind the complex interactions of that code base with the wide range of
inputs generated by Leo's users, would the capabilities of Hypothesis
 be of help to you?

There are complexities in Leo's code, but not likely those that Hypothesis
or Pydantic could help with. Startup is an inherently complex process.
Everything would like to execute *last* after everything *else* has been
initialized:-)

Imo, there are few other "complex interactions" in Leo's code. Leo's
classes should work independently of other classes, and (mostly)
independently of calling sequences.

mypy has become an indispensable tool. It verifies that objects actually
have the types I think they have.

Leo has 100% coverage of most of its core code. Full coverage doesn't
guarantee correctness, but it's good enough.

Edward

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/CAMF8tS1bmbpOt4rAwzyyoua4pUpbfuptiomjUmpXtpNuOQZsAA%40mail.gmail.com.

Re: Leo 6.7.3 coming soon

[David Szent-Györgyi]

On Monday, April 10, 2023 at 8:04:23 AM UTC-4 Edward K. Ream wrote:

The fix appears to be straightforward, but it points out the folly of 
rushing to release major changes.


If it is difficult for you, who know know Leo's code base so well,  to keep 
in mind the complex interactions of that code base with the wide range of 
inputs generated by Leo's users, would the capabilities of Hypothesis 
 be of help to you? Would 
they be of help to others who lack understanding of those interactions? 

In case it is useful: some time ago, I posted about property-based testing, 
Hypothesis, and Pydantic 
. I 
cannot speak from experience as to effectiveness, the degree of clutter it 
would add to the code base, or the effort required to retro-fit Leo's code 
base, documentation, and sample outlines, but its benefits seem really 
attractive at first reading. 

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/643b403d-2bb4-4364-b16a-e9587dbb5ff9n%40googlegroups.com.

Re: Leo 6.7.3 coming soon

[Thomas Passin]

On Monday, April 10, 2023 at 8:04:23 AM UTC-4 Edward K. Ream wrote:

The fix appears to be straightforward, but it points out the folly of 
rushing to release major changes.


+10! 

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/82d69f1f-9877-42b7-82f2-9031c8d5a807n%40googlegroups.com.

Re: Leo 6.7.3 coming soon

[Edward K. Ream]

On Saturday, April 8, 2023 at 12:13:36 PM UTC-5 Edward K. Ream wrote:

I shall release Leo 6.7.3 as soon as possible after we test PR #3264 
.


Maybe still true, but we must all test 6.7.3 for at least two weeks after 
all path-related PRs have been merged into devel.

Many thanks to Thomas for his excellent testing. He discovered that PR #3264 
 broke @path!

The fix appears to be straightforward, but it points out the folly of 
rushing to release major changes.

Edward

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/ff22a3b9-53cd-4210-b6e6-c55532c20929n%40googlegroups.com.

Re: Leo 6.7.3 coming soon

[Edward K. Ream]

On Saturday, April 8, 2023 at 12:13:36 PM UTC-5 Edward K. Ream wrote:

> I shall release Leo 6.7.3 as soon as possible after we test PR #3264 
.

*Aha* (Thanks, Thomas): Python's os.path 
 module contains all the 
tools Leonistas will ever need. Leo can *easily* apply all the os.path 
conventions to all paths of @ nodes.

os.path can expand os.environ constants, so Leo can *easily *replace $name 
or ${name} by the value of environment variable *name*. 

No need to invent Leo-only conventions! No need for path expressions! 
Bye-bye {{ and }}.

Leo's documentation will give examples of using os.path. Like: @file 
$PROJECT_A_BASE/x.py.

> Those who use path expressions should do a global search/replace (on 
headlines).

Still true, but the revised @ nodes will be safe, standard, and 
likely simpler.

Edward

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/6cbfac61-a5df-4829-99b2-52daf475246cn%40googlegroups.com.