Re: Issue #3710: EKR's last lecture

On Sat, Dec 30, 2023 at 12:15 AM Edward K. Ream wrote So yes, I would use nim if I could. > > I've just glanced at nim code. "I" instead of "if"?? > Never mind. nim's intro page clearly shows python-like keywords. I thought I was reading nim code at https://rosettacode.org/wiki, but I must hav

Re: Issue #3710: EKR's last lecture

On Wednesday, December 27, 2023 at 12:37:23 PM UTC-6 offray wrote: [Rust] seems a pretty good project for such migrations and yes, with a lot of heavy lifting already done. I'm plowing through the interactive rust manual and the actual RustPython code. It's a

Re: 🚀 LeoInteg 1.0.17 Released

On Fri, Dec 29, 2023 at 7:52 AM Thomas Passin wrote: > Far from a guru! I suppose I'm not really a newbie any more, but I'm still stumbling around. Humility will not get you off the hook. Hehe. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor"

Re: 🚀 LeoInteg 1.0.17 Released

As a first response to overcoming Viktor's problem, I suggest that Felix could find a way to have LeoInteg open a venv and launch Python from that. This would require a new setting that would take priority over the current setting for the Python executable. (Sorry, Felix, I hate to suggest more

Re: 🚀 LeoInteg 1.0.17 Released

On Friday, December 29, 2023 at 8:49:18 AM UTC-5 Edward K. Ream wrote: On Fri, Dec 29, 2023 at 7:35 AM Thomas Passin wrote: > I may be one of the few people who realizes how inconsistent the installation situation is because I run around 8 or 10 different distros and distro versions from time

Re: 🚀 LeoInteg 1.0.17 Released

On Fri, Dec 29, 2023 at 7:35 AM Thomas Passin wrote: > I may be one of the few people who realizes how inconsistent the installation > situation is because I run around 8 or 10 different distros and distro > versions from time to time to make sure a certain software package runs right > on Linu

Re: 🚀 LeoInteg 1.0.17 Released

>> Thomas, is this a documentation issue for Leo, or must setup.py change? > I don't know; I'll have to think about it some more. ... > I suppose we should do something but I can't see what it would be that would > work across all distros. Thanks for looking into this! Edward -- You received t

Re: 🚀 LeoInteg 1.0.17 Released

I may be one of the few people who realizes how inconsistent the installation situation is because I run around 8 or 10 different distros and distro versions from time to time to make sure a certain software package runs right on Linux. Naturally I try to install Leo and GF4 on those distros.

Re: 🚀 LeoInteg 1.0.17 Released

On Friday, December 29, 2023 at 6:37:55 AM UTC-5 Edward K. Ream wrote: On Fri, Dec 29, 2023 at 3:44 AM Viktor Ransmayr wrote: tbp1...@gmail.com schrieb am Freitag, 29. Dezember 2023 um 00:54:50 UTC+1: You referring to needing to use *--break-system-packages*, is that right? Big sigh. Anot

Re: 🚀 LeoInteg 1.0.17 Released

On Fri, Dec 29, 2023 at 3:44 AM Viktor Ransmayr wrote: > > tbp1...@gmail.com schrieb am Freitag, 29. Dezember 2023 um 00:54:50 UTC+1: > > You referring to needing to use *--break-system-packages*, is that right? > > Big sigh. Another example of a Python "improvement" breaking existing code or pra

Re: 🚀 LeoInteg 1.0.17 Released

Hello Thomas, tbp1...@gmail.com schrieb am Freitag, 29. Dezember 2023 um 00:54:50 UTC+1: You referring to needing to use *--break-system-packages*, is that right? Yes. I don't see this as a Leo issue. It is an issue between 'LeoInteg' & 'Leo', if the underlying Linux distro has adopte

Re: 🚀 LeoInteg 1.0.17 Released

Hello Felix, Félix schrieb am Freitag, 29. Dezember 2023 um 00:01:48 UTC+1: ... Concerning the upgrade/installation of Leo itself, It is directly related to Leo, and thus you should file an issue with Leo itself if you think this can help other users in the future. It is not that easy - an