discovery: psutil module, and: history tracer control buttons

Hi All, I've been having some fun this evening exploring a new-to-me and so-far-excellent cross platform module for controlling and monitoring computer processes from inside python: *psutils* (https://github.com/giampaolo/psutil). It is more than worth the price of admission (time spent

beautify node and tree gone/replaced?

Are the beautify-node and beautify-tree commands supposed to be gone? If yes, they've presumably replaced with something else I've missed. What pray tell? Log window: Leo 6.3-devel, devel branch, build da6df05a98 2020-03-16 16:20:41 -0500 Python 3.6.8, PyQt version 5.12.6 linux {...snip...}

Re: Some excellent pytest articles/presentations

On Mon, Mar 16, 2020 at 4:08 PM Brian Theado wrote: > > > On Mon, Mar 16, 2020 at 6:23 AM Edward K. Ream > wrote: > >> When I awoke this morning I understood why you might suggest this. It >> would, supposedly, make it possible to instantiate multiple instances of >> the LeoApp class. I have

Re: Matt: there seems to be a duplicate clean-up-root branch

On Mon, Mar 16, 2020 at 3:49 PM Matt Wilkie wrote: > I merged a branch called clean-up-root a few days ago. >> > Am I correct that the remaining clean-up-root branch can be deleted? If >> so, please do so. >> > > I split the work into clean-up-root and clean-up-roor-*pr* to separate > the more

Re: Viewrendered3 Fails to Start With Leo 6.2-b1 But Works With Leo 6.1-final

On Mon, Mar 16, 2020 at 3:42 PM Matt Wilkie wrote: > The problem I'm having is that my repo in my account on Github somehow got >> messed up, and I haven't been able to nuke it, repair it, or get it to >> fully update itself from the Leo upstream. > > Thanks, Matt, for these suggestions. Hope

Re: Viewrendered3 Fails to Start With Leo 6.2-b1 But Works With Leo 6.1-final

On Mon, Mar 16, 2020 at 11:36 AM Thomas Passin wrote: > > So I should change leo_vr3.css to vr3_rst.css? >> > > Yes, please do that. > Done in 6.2 and devel branches. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from

Re: Some excellent pytest articles/presentations

On Mon, Mar 16, 2020 at 6:23 AM Edward K. Ream wrote: > When I awoke this morning I understood why you might suggest this. It > would, supposedly, make it possible to instantiate multiple instances of > the LeoApp class. I have just created #1537 >

Re: Matt: there seems to be a duplicate clean-up-root branch

> > I merged a branch called clean-up-root a few days ago. > Am I correct that the remaining clean-up-root branch can be deleted? If > so, please do so. > I split the work into clean-up-root and clean-up-roor-*pr* to separate the more time consuming stuff from the easy parts. The -pr branch

Re: Viewrendered3 Fails to Start With Leo 6.2-b1 But Works With Leo 6.1-final

> > The problem I'm having is that my repo in my account on Github somehow got > messed up, and I haven't been able to nuke it, repair it, or get it to > fully update itself from the Leo upstream. Thomas I think maybe what happened is that at some point in history a new local branch named

Re: launchLeo on ubuntu: Reuse existing editor process?

I don't know about how to enforce single session (bring the already running application to the front) from a menu or desktop link, but for creating the menu link there is a script in Leo: "Settings >> Open desktop integration" and then see [add-desktop-links] or [remove-desktop-links]. They're

Re: Viewrendered3 Fails to Start With Leo 6.2-b1 But Works With Leo 6.1-final

On Monday, March 16, 2020 at 12:06:39 PM UTC-4, Edward K. Ream wrote: > > On Mon, Mar 16, 2020 at 10:57 AM Thomas Passin > wrote: > > > The correct file name is "vr3_rst.css". > > So I should change leo_vr3.css to vr3_rst.css? > Yes, please do that. I just looked at the viewrendered.py file in

Re: Viewrendered3 Fails to Start With Leo 6.2-b1 But Works With Leo 6.1-final

On Mon, Mar 16, 2020 at 10:57 AM Thomas Passin wrote: > The correct file name is "vr3_rst.css". So I should change leo_vr3.css to vr3_rst.css? Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop

Re: Viewrendered3 Fails to Start With Leo 6.2-b1 But Works With Leo 6.1-final

On Monday, March 16, 2020 at 10:56:51 AM UTC-4, Edward K. Ream wrote: > > > Your copy of qt_gui.py was, once again, not formatted properly. Neither > file changed the name of the stylesheet. > I probably should not have included the qt_gui.py at all. I just wanted to make sure it didn't get

Re: About rust and python

On Mon, Mar 16, 2020 at 10:06 AM vitalije wrote: > You should take a look at [PyOxidizer , PyO3 , neon , and mini_leo ]. Thanks for these links.

Re: About rust and python

> > it loads LeoPyRef.leo along with all at-file nodes in less than 80ms. > > The extension module has also an iterator of nodes which iterates tree of > 9250 nodes in 7ms. Drawing tree with such an iterator shouldn't take too > long. > > Oh, and it doesn't use multi processor cores at all.

Re: About rust and python

You should take a look at the PyOxidizer I haven't used it yet, but it seems promising. The other one you should look at (and I have been using it) is PyO3 , for writing python extensions in rust. There is also neon

Re: About rust and python

On Monday, March 16, 2020 at 6:17:17 AM UTC-5, Edward K. Ream wrote: > [I might study] RustPython ...just to see what real rust code looks like. I have just created #1538

Re: Viewrendered3 Fails to Start With Leo 6.2-b1 But Works With Leo 6.1-final

On Mon, Mar 16, 2020 at 8:55 AM Thomas Passin wrote: I found two other issues, both fixed in the attached zip file: > Your copy of VR3.py corrected the call to g.toUnicode(s). Your copy of qt_gui.py was, once again, not formatted properly. Neither file changed the name of the stylesheet. So

Re: About rust and python

On Mon, Mar 16, 2020 at 9:02 AM Thomas Passin wrote: >> Imo, RustPython is not likely to go anywhere, unless a company like Google or Apple supports it. For Python's core devs, RustPython probably looks like a fork. Having just emerged from the trauma of the Python 3 fork, my guess is that they

Re: Some excellent pytest articles/presentations

On Mon, Mar 16, 2020 at 9:06 AM Thomas Passin wrote: > > > On Monday, March 16, 2020 at 6:23:50 AM UTC-4, Edward K. Ream wrote: > >> >> As noted in the issue, it's not clear whether changing `g.app` to `self` >> in the LeoApp class would make any real difference. It might well mislead >> people.

Re: Some excellent pytest articles/presentations

On Monday, March 16, 2020 at 6:23:50 AM UTC-4, Edward K. Ream wrote: > > As noted in the issue, it's not clear whether changing `g.app` to `self` > in the LeoApp class would make any real difference. It might well mislead > people. > I always thought that you had used this kind of idiom as a

Re: About rust and python

On Monday, March 16, 2020 at 7:17:17 AM UTC-4, Edward K. Ream wrote: > > In the "What's Next post > I > said: > > "As far as wasm [WebAssembly] goes, rust has a (temporary?) advantage over > python, because wasm doesn't yet

Re: Viewrendered3 Fails to Start With Leo 6.2-b1 But Works With Leo 6.1-final

On Monday, March 16, 2020 at 8:32:24 AM UTC-4, Edward K. Ream wrote: > > Alright. I've fixed the problem in vr3. Hope you recover from your > problems :-) > Thanks. In addition, I found two other issues, both fixed in the attached zip file: 1) The name of the RsT stylesheet was obsolete(

Re: Viewrendered3 Fails to Start With Leo 6.2-b1 But Works With Leo 6.1-final

On Mon, Mar 16, 2020 at 7:15 AM Thomas Passin wrote: > > > On Monday, March 16, 2020 at 8:08:57 AM UTC-4, Thomas Passin wrote: > > I started to use --init-docks when my body and tab panes got so messed up > they were unusable and I couldn't get them into a sensible configuration > again. >

Re: Viewrendered3 Fails to Start With Leo 6.2-b1 But Works With Leo 6.1-final

On Mon, Mar 16, 2020 at 7:13 AM Thomas Passin wrote: > > On Monday, March 16, 2020 at 6:58:21 AM UTC-4, Edward K. Ream wrote: > >> >> Thomas, I'm not sure why this was a mysterious problem for you. I >> continue to suspect something is not right on your end. >> >> Please verify, using gitk, that

Re: Viewrendered3 Fails to Start With Leo 6.2-b1 But Works With Leo 6.1-final

On Monday, March 16, 2020 at 8:08:57 AM UTC-4, Thomas Passin wrote: > > There is one specific thing that is failing: > > g.app.dock is returning False. When that happens, the rest of > create_pane() gets skipped (and of course my plugin won't work). It is > supposed to be returning True when

Re: Viewrendered3 Fails to Start With Leo 6.2-b1 But Works With Leo 6.1-final

On Monday, March 16, 2020 at 6:58:21 AM UTC-4, Edward K. Ream wrote: > > Thomas, I'm not sure why this was a mysterious problem for you. I continue > to suspect something is not right on your end. > > Please verify, using gitk, that you see the changes I made in both the 6.2 > and devel

Re: Viewrendered3 Fails to Start With Leo 6.2-b1 But Works With Leo 6.1-final

There is one specific thing that is failing: g.app.dock is returning False. When that happens, the rest of create_pane() gets skipped (and of course my plugin won't work). It is supposed to be returning True when docks are in use. This happens when I start Leo with --init-docks. When I

About rust and python

In the "What's Next post I said: "As far as wasm [WebAssembly] goes, rust has a (temporary?) advantage over python, because wasm doesn't yet support garbage collection." Well, what about writing the python interp in rust?

Re: Viewrendered3 Fails to Start With Leo 6.2-b1 But Works With Leo 6.1-final

On Monday, March 16, 2020 at 5:39:23 AM UTC-5, Edward K. Ream wrote: > I'll look into this. Fixed in both the 6.2 and devel branches. Thomas, I'm not sure why this was a mysterious problem for you. I continue to suspect something is not right on your end. Please verify, using gitk, that you

Re: Viewrendered3 Fails to Start With Leo 6.2-b1 But Works With Leo 6.1-final

On Sun, Mar 15, 2020 at 10:53 PM Thomas Passin wrote: Running Leo 6.2-b1, VR3 fails to create its toolbar (which causes VR3 to > fail), but the very same file, viewrendered3.py, works as expected running > Leo 6.1-final. > I'll look into this. VR3 must either work with the 6.2 code base or be

Re: Viewrendered3 Read For Beta Testing

On Sun, Mar 15, 2020 at 4:23 PM Thomas Passin wrote: Now that's funny. I just imported qt_gui.py in my Leo outline - the same > qt_gui.py file I zipped up for you - and neither pyflakes nor pylint found > anything to complain about. Maybe your pylint settings are different from > mine. I

Re: Viewrendered3 Read For Beta Testing

On Sun, Mar 15, 2020 at 3:46 PM Thomas Passin wrote: > > > On Sunday, March 15, 2020 at 11:35:26 AM UTC-4, Edward K. Ream wrote: >> >> >> In future, please run pylint on your code. It will catch these kinds of >> things. >> > > I thought that pyflakes was doing that job now. > Pyflakes and

Re: Some excellent pytest articles/presentations

On Sunday, March 15, 2020 at 3:41:09 PM UTC-5, Edward K. Ream wrote: On Sun, Mar 15, 2020 at 1:29 PM Brian Theado wrote: > > What do you think about the following specific suggestion? >> >> Change all 'g.app' references in the methods of the LeoApp class to >> 'self'. Or add 'app = self' to the