I just found that the problem went away when I deleted the Leo database directory. I added a comment to that effect in #1444. It must have something to do with the fact that I have used both Leo 5.9/python 2.7/QT4 and Leo 61/python 3.8/QT4 alternately. Somehow some things cached in the database must have been getting read by Leo even though their entries were some time in the past.
I did an very time-consuming hunt for anyplace in the 6.1 code base where QT4 might have been getting invoked by mistake, but found nothing. On Friday, December 6, 2019 at 9:39:49 AM UTC-5, Edward K. Ream wrote: > > Rev 028f4b attempts a fix for #1444 > <https://github.com/leo-editor/leo-editor/issues/1444> (many errors > during startup) without really knowing what is going on. > > The traceback indicates that line 607 in leoCache.py may be to blame. > > The old code catches only KeyError; the new code catches all Exceptions. > The traceback references PyQt4, so perhaps there is some > installation-dependent problem/strangeness. > > I am wondering whether this fix might just fix #1445 as well. Clearly, > something unusual is going on, because very few people seem to be affected > by either bug. > > 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/c6e78157-d0a9-4231-aacf-9d3a8dc32095%40googlegroups.com.
