Last time I tried it with *devel*, Leo wouldn't even run with the latest version of pyqt6 (6.11). And even if it will by now, some plugins probably won't work correctly or at all. So I'm inclined to say not to worry about it at this preliminary release (pre-6.4 final), and not to make it a major goal. If it turns out to happen, fine. With VR3, rendering will be crippled until we get the new equivalent of webEngineView, possibly in the fall. Freewin will be in better shape but still won't do the rendered view well but you don't need it to use the plugin).
The only gotcha I can think of is if a user were to install some other non-Leo package that in turn wanted pyqt6. Perhaps Leo could have a command-line switch not to use pyqt6 if pyqt5 were available. That would require both to be available and both to be imported, and some finagling with the name assignments after the imports. But it should be workable. I 've been managing the use of pyqt6 in this way: after installation, I moved all the pyqt6 files out of *site-packages* to some other directory. When I want to try pyqt6, I set the PYTHONPATH environmental variable to point to the new location. This lets me try different pyqt6 versions, and to keep using pyqt5 by default, in a fairly convenient way (I don't seem to coexist well with venvs). On Tuesday, July 6, 2021 at 2:20:31 PM UTC-4 Edward K. Ream wrote: > Leo does not need to support Qt6 for Leo 6.4b1. Indeed, b1 is focused > solely on supporting the leoInteg project. > > Yes, Leo must eventually support Qt6. The question is, does Leo need to > support Qt6 for Leo 6.4 final? I am inclined to say no because that will > give us more time for testing. Otoh, perhaps we should just blast away. > > Your comments, please. > > 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/33d9a491-9164-4400-a94e-230fedb58c16n%40googlegroups.com.
