Re: Discuss: Release Leo only via GitHub?

On Sat, Jan 20, 2024 at 5:07 PM Thomas Passin wrote: > Yes, running pip on requiremenst.txt is the standard way. I also know > that currently requirements.txt does not contain the actual dependencies > (which can be changed, of course). I was just thinking about whether a new > user would have

Re: Discuss: Release Leo only via GitHub?

Yes, running pip on requiremenst.txt is the standard way. I also know that currently requirements.txt does not contain the actual dependencies (which can be changed, of course). I was just thinking about whether a new user would have a problem with using pip this way, having already manually

Re: Discuss: Release Leo only via GitHub?

On Sat, Jan 20, 2024 at 3:23 PM Thomas Passin wrote: > I think that would be all right, although sometimes I have trouble finding > the release files when I want to get an app from GitHub. My main concern > would be how to make it painless for a new user to get the dependencies > installed. >

Re: Discuss: Release Leo only via GitHub?

I think that would be all right, although sometimes I have trouble finding the release files when I want to get an app from GitHub. My main concern would be how to make it painless for a new user to get the dependencies installed. On Saturday, January 20, 2024 at 2:14:18 PM UTC-5 Edward K.

Re: Alpha Geometry: A wow paper from Nature

On Saturday, January 20, 2024 at 2:14:05 PM UTC-6 Edward K. Ream wrote: >From Figure 3: a, We first sample a large set of random theorem premises. b, We use the symbolic deduction engine to obtain a deduction closure. *This returns a directed acyclic graph of statements.* I read the caption

Re: Alpha Geometry: A wow paper from Nature

On Saturday, January 20, 2024 at 2:01:32 PM UTC-6 Edward K. Ream wrote: Here is the link . >From Figure 3: a, We first sample a large set of random theorem premises. b, We use the symbolic deduction engine to obtain a deduction closure.

Alpha Geometry: A wow paper from Nature

Here is the link . I was able to access the paper without a subscription. The solution is left as an exercise for the reader. We haven't seen anything yet :-) Edward -- You received this message because you are subscribed to the Google

Re: Leo 6.7.7 released

On Sat, Jan 20, 2024 at 8:16 AM Thomas Passin wrote: > All right, now the pip distro reports Leo 6.7.7. > > BTW, pip won't upgrade an existing package to one of the same release. > There's probably some better way, but I handled it by deleting 6.7.7 and > its install directory from Python's

Discuss: Release Leo only via GitHub?

I am at the end of my patience with PyPI : - The process is error-prone, as we have just seen. - PyPI is thwarting the upgrade of leo-6.7.7.tar.gz. I don't know why. The error message seems wrong. - Even with help, 2-factor authentication is too

Re: Leo 6.7.7 released

On Sat, Jan 20, 2024 at 9:41 AM Zoom.Quiet wrote: > supper cool, > had to upgrade ASAP. > Thanks for testing :-) 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

Re: Leo 6.7.7 released

supper cool, had to upgrade ASAP. Thomas Passin 于2024年1月20日周六 22:16写道： > > All right, now the pip distro reports Leo 6.7.7. > > BTW, pip won't upgrade an existing package to one of the same release. > There's probably some better way, but I handled it by deleting 6.7.7 and its > install

Re: Leo 6.7.7 released

All right, now the pip distro reports Leo 6.7.7. BTW, pip won't upgrade an existing package to one of the same release. There's probably some better way, but I handled it by deleting 6.7.7 and its install directory from Python's site-packages directory (the one in the user's location if

Re: Leo 6.7.7 released

On Thursday, January 18, 2024 at 1:12:51 PM UTC-6 Edward K. Ream wrote: Leo https://leo-editor.github.io/leo-editor/ 6.7.7 is now available on GitHub and pypi . The latest GitHub release