The printout should have included the exception, according to the code in runLeo. Does something else get printed before the message that you quoted?
On Wednesday, October 19, 2022 at 7:01:35 AM UTC-4 Edward K. Ream wrote: > On Wed, Oct 19, 2022 at 1:38 AM Richard Twyning < > [email protected]> wrote: > > >> I'm getting... >> *** Leo could not be started *** >> > ... > >> Is there anything more specific I can look at that tells me exactly >> what's missing? >> > > Excellent question. > > The message comes from runLeo.py. I would do the following: > > - Edit leo/core/runLeo.py in your favorite text editor. > - After line 39, insert these two lines (right before the 'try' statement): > > import pdb > pdb.set_trace() > > Now invoke `python runLeo.py` from the command line. You should drop into > python's pdb debugger <https://docs.python.org/3/library/pdb.html>. > > pdb will (eventually) show the exception that caused the message, so you > can just type 'n' until you see the exception. That may be enough of a > hint. If not, you can rerun `python runLeo.py`, choosing 's' instead of > 'n' to trace into the import logic. > > HTH. Please let me know if this strategy doesn't work. > > 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 on the web visit https://groups.google.com/d/msgid/leo-editor/3674a769-668f-44f2-8282-9842289949can%40googlegroups.com.
