Here is how I have been testing with either pyqt5 or 6. No need for separate virtual environments.
After I install pyqt6, I go to the installation location (site-packages) and move all the pyqt6 folders (including the *.dist-info ones) somewhere else. In my case I'm using c:\Tom\qt623. When I want to run with pyqt6, I set PYTHONPATH=c:\Tom\qt623 When I want to run with pyqt5, I unset PYTHONPATH. It would be easy to make a batch file to do this and launch Leo, but I haven't bothered so far. When you copy all the folders including the *.dist-info ones, then pip doesn't know that pyqt6 is installed, unless PYTHONPATH has been set. That's a benefit when you need to work with different versions. On Tuesday, February 15, 2022 at 5:42:57 PM UTC-5 Edward K. Ream wrote: > On Tue, Feb 15, 2022 at 11:27 AM tbp1...@gmail.com <tbp1...@gmail.com> > wrote: > >> No need to simplify existing code that is working, since it's already >> been adjusted for both. mypy and pylint are reasonable concerns, and maybe >> there will turn out to be a simple way to handle them. So let's not rush! > > > I agree. However, I may create a Qt6 branch to see whether mypy and pylint > would work better. > > 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 leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/a3b5c67e-b20a-4d9c-b3a4-cf8d1aeb11e9n%40googlegroups.com.
