#1274 <https://github.com/leo-editor/leo-editor/issues/1274> recommends
that leoQt.py should return None for everything when in g.in_bridge is true.
That can easily be done by setting fail = g.in_bridge at the start of
leoQt.py. However, the code presently is:
fail = False
# New for TravisCI tests: allow imports from the Leo Bridge.
so I suspect the proposed change would cause TravisCI to barf.
*Thinking out loud*
So now we have a dilemma. #1274 arises because it's actually not
reasonable, in general, to attempt Qt imports from the bridge. But it
appears we must do so in order to support TravisCI.
Could we just ignore this issue and leave leoQt as it is? I can only get
the failure in the specific case of calling PyzoInterface.patch_pyzo from
inside pyzo.start.
*Summary*
The hacks in the bridge branch
<https://github.com/leo-editor/leo-editor/commit/6a81e6c9fd35740eb536c5be04f77163c422e1df>
make imports aware of g.in_bridge. This is the worst kind of special case.
I would rather live with the present code than tolerate these hacks.
Any comments or suggestions?
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/b6c9f1a6-d009-468e-b049-07aa887deaf8%40googlegroups.com.
