I'm no venv expert, that's for sure. I *think* that packages installed into a venv can be symlinked from the non-venv installation if they are the same version. Better try to check that, though. It sounds like that what's happening in your case. It didn't seem to in mine. All a mystery.
If it were my system, I would delete all the Qt* files in the non-venv install, clean out the entire venv, and run pip -r requirements.txt in the venv. As long as you get rid of all the qt* files and folders including the dist* ones, you will get all new files. If they still didn't work, I would repeat the cleanup and install a lower version of PyQt and the WebEngineView. On Wednesday, November 6, 2024 at 2:40:40 AM UTC-5 jkn wrote: > > This is turning into a venv thread rather than anything else, but anyway... > > - FWIW I have successfully installed Leo (and VR3 etc.) on two Linux > machines via venv. > - on my problematic Windows machine, in a venv, how come all the installed > requirements seem to be *not* in the venv? I was expecting them to under > <venv>\Lib\site-packages, or similar. > > but if I (re-)run > > <venv>\leo-editor> python3 - m pip install -r requirements.txt > > then I get a long list of requirements (including PyQt6 ones) already > satisfied ... in a location <user>\appdata\local\... > > J^n > > On Tuesday, November 5, 2024 at 2:16:37 PM UTC [email protected] wrote: > >> Freewin falls back to using a QTextBrowser if a QWebEngineView isn't >> present. That only affects the rendered view, not the editor view. The >> QTextBrowser's rendering is limited compared with the QWebEngineView but >> that won't really matter for most nodes. >> >> I have removed all the PyQt* files from site-packages and re-installed. >> When you remove all those *dist* files, pip doesn't know that the >> package had ever been installed. >> >> I wonder if a revised WebEngine package got into PyPi recently and it's >> accidentally missing the DLL. A downgrade might work in that case. >> >> On Tuesday, November 5, 2024 at 8:49:58 AM UTC-5 jkn wrote: >> >>> Hi Thomas - yes, all good suggestions. I have these and/or similar on my >>> list to check when I have a few minutes. I did look for the .dll yesterday >>> but didn't note down the results >>> >>> I am not desperate enough to use VR3 to try your option (3), I really >>> just want to have VR3 there in my 'cutting-edge' ;-: Leo to try a few >>> experiments. >>> >>> I will update in a bit >>> >>> Thanks, J^n >>> >>> >>> On Tuesday, November 5, 2024 at 1:10:22 PM UTC [email protected] wrote: >>> >>>> That seems like just what I did. You might look at the Qt files in >>>> Python's Lib\site-packages in the venv and see if they are symlinked to >>>> the >>>> files in the main (non-vm) install. I don't know when files in a new VM >>>> get >>>> symlinked and when they don't. If they are symlinked then I only have >>>> three ideas left: >>>> >>>> 1. Delete all Qt files yourself and re-install their packages one by >>>> one with pip; >>>> 2. Downgrade PyQt and the WebEngineView to an earlier version. >>>> >>>> If they are not symlinked I would say to do the same but inside the >>>> venv's site-package directory. >>>> >>>> 3. One more possibility would be to delete everything in the venv and >>>> re-create it (or make a new one) and to pip-install leo 6.8.1. This >>>> version of Leo may (and probably will) run. Then just use that venv to >>>> run >>>> your Leo clone. >>>> >>>> Maybe #3 should be the first thing to try. >>>> >>>> Oh, yes, can you search for that DLL by name to see if it's actually >>>> present on the computer? >>>> >>>> On Tuesday, November 5, 2024 at 7:49:42 AM UTC-5 jkn wrote: >>>> >>>>> Hmm - I think I have just done what you suggest above and get the same >>>>> error as before. ie: >>>>> >>>>> - create a virtual environment >>>>> - activate it >>>>> - git clone leo... >>>>> - cd leo-editor >>>>> - python3 -m pip -r requirements.txt >>>>> ... >>>>> - python3 launchleo.py >>>>> >>>>> and (if VR3 is enabled) I get the same error as before (NB: not sure >>>>> it is exactly what you were reporting): >>>>> >>>>> [image: Capture.PNG] >>>>> - >>>>> >>>>> On Monday, November 4, 2024 at 7:14:10 PM UTC [email protected] wrote: >>>>> >>>>>> After a kernel update on my Linux Mint VM just now, I got the same >>>>>> error - no PyQt6-WebEngine. Upgrading the PyQt6-x packages didn't fix >>>>>> the >>>>>> error. I installed using requirements.txt into a venv and running in >>>>>> that >>>>>> venv VR3 finds the QWebEngine and runs. >>>>>> >>>>>> On Monday, November 4, 2024 at 6:51:53 AM UTC-5 jkn wrote: >>>>>> >>>>>>> Hmm, slightly separate point, but now I am trying to replicate >>>>>>> things (enabling viewrendered3) on my Windows machine... >>>>>>> >>>>>>> I am getting a Windows Error popup: ... Qt6WebEngineCore.dll was not >>>>>>> found... >>>>>>> >>>>>>> Leo itself doesn't have an error from vr3. >>>>>>> >>>>>>> I've tried to install/re-install a few things via pip, but no >>>>>>> success. Any pointers? >>>>>>> >>>>>>> Thanks, jon N >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Monday, November 4, 2024 at 2:44:50 AM UTC [email protected] >>>>>>> wrote: >>>>>>> >>>>>>>> On Sunday, November 3, 2024 at 5:55:10 PM UTC-5 jkn wrote: >>>>>>>> >>>>>>>> Anyway - after putting 'freewin.py' in myLeoSettings.leo (and >>>>>>>> installing QtWebEngineView for PyQt6 - interestingly VR3 does not seem >>>>>>>> to >>>>>>>> give a warning if this is not installed) - I seem to be making >>>>>>>> progress, >>>>>>>> both with VR3 and with Freewin. >>>>>>>> >>>>>>>> >>>>>>>> Freewin will fall back to using a QTextBrowser for the rendered >>>>>>>> view if QWebEngineView isn't installed, and it should emit a message >>>>>>>> about >>>>>>>> that. VR3 can't work without a QWebEngineView, and it's supposed to >>>>>>>> emit a >>>>>>>> message about a missing QWebEngineView . Maybe some recent change has >>>>>>>> stepped on the message, but I don't recall any changes in that part of >>>>>>>> the >>>>>>>> code. >>>>>>>> >>>>>>> -- 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 visit https://groups.google.com/d/msgid/leo-editor/36f8a141-a79f-4cac-93d9-274c3b4e692fn%40googlegroups.com.
