On Sunday, April 19, 2020 at 8:37:38 PM UTC-4, Matt Wilkie wrote: > > In order for the bare command leo to work, the operating system has to >> know that it's a Python file and that it's supposed to open a Python file >> using Python. Sometimes this chain of identification doesn't get set up >> right. It seems like that was the problem when you got this error message: >> >> leo : The term 'leo' is not recognized as the name of a cmdlet, function, >> script file, or operable program. >> >> It will not get set up if you just download a zip file and run from it. >> A pip install *may* do it, but I'm not sure. >> > > Yes, it will. >
Well, look at that. My stock Leo pip install, which is 5.9, does launch just by typing leo. Of course, that's my old python 2.7/qt4 installation which I never run anymore. I forget if I installed Leo with the installer or with pip for that one. My system path includes c:\Python27\Scripts. That Scripts directory contains a leo.exe. When I installed Python 3.8, its location never got added to the system path. I have a batch file that disables the python 2.7 path steps and adds the Python38/Scripts directory. After I run it, then I have a leo command that launches Leo with the Python 3.8 setup. I suppose I never discovered it because I normally launch from a console window, rather than using pythonw. What's more, if I set PYTHONPATH to point to my git clone location, the leo command launches Leo from there instead of from the standard install. Excellent - that's just what I would want. OTOH, I don't see a leo.exe command in the Git clone. I suppose that it gets built somewhere for the Leo wheel for Windows, is that right? -- 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 on the web visit https://groups.google.com/d/msgid/leo-editor/765cddef-6f10-4e37-9fc3-16d5d8510fec%40googlegroups.com.
