On Wed, Nov 20, 2024 at 12:48 PM Thomas Passin <[email protected]> wrote:
> Let's continue this investigation on the GitHub issue thread, shall we? > I'd rather not. I agree that py -m leo.core.runLeo works as expected in all the cases. My >> tests all show the same. What *doesn't *work as expected is running py >> leo\core\runLeo.py when the working directory is leo-editor. >> > By "py" I'm assuming that you mean Python's launcher, *py.exe*. We are back to the bingo. Leo's *devs *should use their own local python script: *python.cmd* or a *python script or alias* on linux/MacOS machines. Either way, Leo's devs are responsible for choosing the correct python. People who pip install leo shouldn't have problems. None have been reported. Leo works. If devs have a problem, *they *are responsible for the workarounds. I can't debug devs' installations. 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 email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/leo-editor/CAMF8tS0tMpG%3DbBx_Uk%3D%2BTamk_DpUkKN00QjQ-%2B9c-FjM52CF1Q%40mail.gmail.com.
