Hello Edward, hello Matt, Am Sa., 28. Dez. 2019 um 19:26 Uhr schrieb Viktor Ransmayr < [email protected]>:
> > I just noticed something interesting/ strange/ weird. > > Actually two issues: > > First: Leo requires that the tkinter module is configured in the Python > installation. > > (Backgound: I just upgraded to Python 3.7.6 - and - decided to de-select > everything but pip ...) > > Second: I noticed this only, when I started w/o an existing '~/.leo' > directory. > > The traceback I receive is: > > ... > > As soon as I re-use my previously saved '~/.leo' directory, the > ModuleNotFoundError disappears ... > > Can you please explain > > * why the module 'tkinter' is required, although PyQt is used as the GUI > framework - and - > Analyzing Leo's content & dependencies a bit more, I found at least one reason myself: * Leo does support the GUI-Options: [ browser | console | null | qt ] - and - at least the console option does require 'tkinter' as well. So this now looks only like a possible future 'refactoring' task to me, in case a split into smaller sub-components/-packages is ever planned for Leo ... > * secondly, why the problem goes away, if I'm using "old/ saved" '~/.leo' > content ... > This is the remaining question I'd really would like to get an explanation. With kind regards, Viktor -- 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/CAAeSrGL1Dz_6kKVhTsG2HW5Wn%2B7_LJi9p_-5jzUNKzBKufgCOA%40mail.gmail.com.
