Leo 6.0 final released

[Edward K. Ream]

Leo 6.0 final, http://leoeditor.com, is now available on GitHub.

Many thanks to all who have contributed to this release.

The highlights of Leo 6.0

• Leo now requires python 3.6 or above.
  This greatly simplifies Leo's code.
• Leo's default gui uses Qt Docks.
  Use --no-dock to use Leo's legacy gui.
• Several commands now generate clickable links in the Log pane.
  This greatly speeds navigation.
• The usual assortment of bug fixes and minor improvements.

Edward

[Viktor Ransmayr]

Hello Edward,

Am Fr., 2. Aug. 2019 um 19:02 Uhr schrieb Edward K. Ream <edre...@gmail.com>:

Leo 6.0 final, http://leoeditor.com, is now available on GitHub.

Thanks a lot to you & all other Leo developers! - I was able to upgrade a python virtual environment instance using PyPI / pip w/o any problem  from Leo version 5.9 to 6.0 ...

Withkind regards,

VR

[Edward K. Ream]

That's great news!

Edward

[Matt Wilkie]

Thanks a lot to you & all other Leo developers! - I was able to upgrade a python virtual environment instance using PyPI / pip w/o any problem  from Leo version 5.9 to 6.0 ...

Yay! It took awhile to get there with your setup. Thanks for the reports which helped get those bugs sorted out.

-matt

[Matt Wilkie]

Leo 6.0 final, http://leoeditor.com, is now available on GitHub.

I think the v6.0 tag needs to be merged into master branch, or something. Or maybe it's just how Git Extensions shows it to me? (git branching messing me up often).

This is what I see for v6.0 tag:

Commit: db55bd00c94fb8501795284453891ad64ce12af9
Update version to 6.0 final

 

v6.1-dev: Added v6.1-dev tag
v6.0: Added v6.0 tag
Contained in branches: devel
Contained in tags: v6.1-dev, v6.0
Derives from tag: v6.1-dev

and v6.0b1:

Commit: 445dfa149e71a5714714422c9f21c58698218375

Fixed conflicts merging master into 6.0-b1-rel branch

 

v6.0b1: Added v6.0b1 tag
Contained in branches: master, devel
Contained in tags: v6.1-dev, v6.0, v6.0b1
Derives from tag: v6.0b1

 -matt

[Edward K. Ream]

On Fri, Aug 2, 2019 at 4:04 PM Matt Wilkie <map...@gmail.com> wrote:

Leo 6.0 final, http://leoeditor.com, is now available on GitHub.

I think the v6.0 tag needs to be merged into master branch, or something.

gitk shows all is well.

Matt, I see that you pushed to the black branch.  What's going on?

Edward

[Edward K. Ream]

On Sat, Aug 3, 2019 at 6:13 AM Edward K. Ream <edre...@gmail.com> wrote:

gitk shows all is well.

For a panicky moment I thought perhaps I hadn't pushed to master, but I did.  The latest rev on master is db55bd0, both on my machine and in the master branch. 

gitk shows the following labels on this branch:  v6.0, v6.1-dev, 6.0-final-rel, master, remotes/origin/6.0-final-rev, remotes/origin/master.  But not remotes/origin/v6.0.  Is that a problem?

Edward

[Matt Wilkie]

gitk shows the following labels on this branch:  v6.0, v6.1-dev, 6.0-final-rel, master, remotes/origin/6.0-final-rev, remotes/origin/master.  But not remotes/origin/v6.0.  Is that a problem?

I'm seeing the same with gitk and I honestly don't know if it's a problem. I was hoping you knew! At any rate, v6.0 self published to PyPi so Travis is fine with it. I guess we just keep going and wait and see. :)

In black branch I just added black module as a dependency. In retrospect I can see it's better to wait until the active dev churn has dropped down before pitching something else in.

-matt

[Edward K. Ream]

On Sat, Aug 3, 2019 at 11:23 AM Matt Wilkie <map...@gmail.com> wrote:

gitk shows the following labels on this branch:  v6.0, v6.1-dev, 6.0-final-rel, master, remotes/origin/6.0-final-rev, remotes/origin/master.  But not remotes/origin/v6.0.  Is that a problem?

I'm seeing the same with gitk and I honestly don't know if it's a problem. I was hoping you knew! At any rate, v6.0 self published to PyPi so Travis is fine with it. I guess we just keep going and wait and see. :)

Yes.  I think this is a good plan.

In black branch I just added black module as a dependency. In retrospect I can see it's better to wait until the active dev churn has dropped down before pitching something else in.

In future, base all your branches on devel, and only make changes to devel (if you're sure) or in one of your own branches, based on devel.  That way you won't step on anyone's toes.

Edward