Of course, if brew was your only package manager, I suppose my suggestions above might not work out so well...
On Sunday, December 13, 2020 at 11:22:59 PM UTC-5 tbp1...@gmail.com wrote: > Many systems have both Python 2.7x and Python 3.x. On several Linux > systems I have, "python" will run Python 2.7x, and "python3" or "python3.8" > will run some version of Python 3. That's probably true for your system, > except that the Python 3 installation got borked somehow. > > I think you should try to uninstall, repair, or install python 3 using > your system's package manager. If you still can't install Python 3.9, see > if you can install Python 3.8. On one of my systems, I have both Python > 3.6 and Python 3.8 installed and running. Python3 and Python3.6 invoke Python > 3.6, and Python3.8 invokes Python 3.8. > > Once you have python 3.x working again, install all the packages you need, > such as Leo, using the "-m" flag like this - > > python3.8 -m pip install leo > > This technique will make sure that python tries to run the right version > of pip, and that the packages will be installed into the right version of > Python. (The "-m" flag tells Python to load a module of that name rather > than a file. Since Python will search its own search path for that module, > it will find the right version of pip.) In the same vein, I normally > launch Leo using the "-m" flag - > > python3.8 -m leo.core.runLeo > > On Sunday, December 13, 2020 at 8:41:31 PM UTC-5 andyjim wrote: > >> I may have lost python. $ python --version yields: Python 2.7.14 :: >> Anaconda, Inc. >> Thought I was supposed to have python 3.x Tried to install 3.9 from >> Python. Says it's installed but doesn't seem to be. >> should I just run a leo install anyway? What install command should I >> use? MacOS >> >> On Sunday, December 13, 2020 at 8:08:24 PM UTC-5 tbp1...@gmail.com wrote: >> >>> Your actual .leo files are probably still there, where ever they were >>> before. You could look for them with find. Then after getting Leo >>> reinstalled, you should be good to go. >>> >>> Otherwise, there's always the backups :) >>> >>> On Sunday, December 13, 2020 at 7:42:01 PM UTC-5 andyjim wrote: >>> >>>> I updated brew. It took an hour or more. After the smoke cleared, Leo >>>> was gone. Would not launch (from icon), and I get this error: >>>> /usr/local/opt/python/bin/python3.7 /usr/local/bin/leo >>>> -bash: /usr/local/opt/python/bin/python3.7: No such file or directory >>>> Likely I have made things worse in my naive, thrashing attempts to fix >>>> it. >>>> At the very least I need to recover the text data in my leo files but >>>> don't know how to do that. >>>> >>> -- 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 leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/b096ba6d-9d39-49d3-9695-e0f2730b6958n%40googlegroups.com.
