Re: A problem with @button write-leoPyRef

On Tue, Sep 20, 2022 at 11:52 AM Thomas Passin wrote: > I'm missing some essential piece of understanding, I think. > > 1. I work on an existing external file (this is mostly what I have done). > This probably won't change LeoPyRef. I commit the changed external file > but don't commit

Re: Discuss: require Qt 6.1+ for Leo 6.7.1?

As always, the problem is most acute for Linux users. Often, the newer packages just aren't available. In some or many Linux distros you are supposed to install things like Qt or even PyQt through the distro's package manager - for example, Debian doesn't have a Python 3.10 package yet. It

Re: Recent changes to devel

On Tue, Sep 20, 2022 at 11:55 AM Thomas Passin wrote: > Great! Can we set up a new milestone, say 6.7.1, so that we can set a > target for new issues? > Done: 6.7.1 issues . Edward -- You received

Discuss: require Qt 6.1+ for Leo 6.7.1?

It's way too late to consider any significant changes to Leo to 6.7.0. *Background* Removing support for Qt5 *is* going to happen. The only question is when. Supporting both Qt5 and Qt6 prevents mypy and pylint from doing thorough checks. The result is the dreaded software rot. Furthermore

Re: Recent changes to devel

Great! Can we set up a new milestone, say 6.7.1, so that we can set a target for new issues? On Tuesday, September 20, 2022 at 12:49:25 PM UTC-4 Edward K. Ream wrote: > Absent new bug reports, I plan no further changes for Leo 6.7.0. Let the > testing continue! > -- You received this

Re: A problem with @button write-leoPyRef

I'm missing some essential piece of understanding, I think. 1. I work on an existing external file (this is mostly what I have done). This probably won't change LeoPyRef. I commit the changed external file but don't commit LeoPyRef. I don't see this as needing a leoPy.leo outline at all.

Re: Recent changes to devel

On Tuesday, September 20, 2022 at 11:14:39 AM UTC-5 Edward K. Ream wrote: > Leo 6.7.0 should be code complete. Now devel is more complete :-) I have just merged PR #2881 into devel. Absent new bug reports, I plan no further changes for Leo

Re: Recent changes to devel

On Tuesday, September 20, 2022 at 11:32:49 AM UTC-5 tbp1...@gmail.com wrote: > I see an improvement in that on my Windows system, the freeze time when > saving LeoPyRef is now only a few seconds instead of the previous 20 - 30 > seconds. That's a worthwhile improvement! > Glad to hear it!

Re: A problem with @button write-leoPyRef

On Tue, Sep 20, 2022 at 11:29 AM Thomas Passin wrote: Looking through the write-leoPyRef, I infer that we are expected to create > a leoPy.leo outline - presumably by saving LeoPyRef by that name, doing all > our work in leoPy, then using the write-leoPyRef command. Is that the idea? Yes.

Re: Recent changes to devel

I see an improvement in that on my Windows system, the freeze time when saving LeoPyRef is now only a few seconds instead of the previous 20 - 30 seconds. That's a worthwhile improvment! On Tuesday, September 20, 2022 at 12:14:39 PM UTC-4 Edward K. Ream wrote: > PR #2877

Re: A problem with @button write-leoPyRef

I'm confused about leoPy.leo vs LeoPyRef.leo. Some time ago, things were changed so that opening leoPy from the File/Open Specific Leo File menu actually opened LeoPyRef. There is no leoPy.leo in the leo/core directory any more. Looking through the write-leoPyRef, I infer that we are

Re: Discuss: remove leoBridgeTest.py and leoDynamicTest.py?

On Monday, September 12, 2022 at 2:03:56 AM UTC-5 Edward K. Ream wrote: > These two files run unit tests using `@test nodes` in .leo files. > > I would like to remove them both. Does anyone still use them? > Hearing no objection, I'll create a new PR that deletes both files. Edward -- You

Recent changes to devel

Today I merged four PRs into devel and made some other changes: PR #2876 : Add annotations to freewin.py. Oops! Another commit was necessary to correct the `@file node`. PR #2877 : Problems

A problem with @button write-leoPyRef

There is an ongoing problem with the script `@button write-leoPyRef`. Iirc, this script is intended to be run from a dev's local leoPy.leo file. There is a big glitch. After running this script Leo's git-diff command reports minimal changes, but actually loading and saving LeoPyRef.leo creates