That use of __pycache__ started later than Python 3.0, I am pretty sure. 
Just to further confuse myself, I am actually jumping between two machines; 
one has .pyc files only in __pycache__, the other has some 'alongside' the 
.py files (2017!). Bu I suspect none of this is relevant to what I am 
seeing. It might possibly indicate that perhaps the behaviour (about 
requiring plugin name to have .py at the end) has changed over the years 
... not sure.

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.

Curiously, I can now no longer replicate the reported behaviour! If I have 
an unsuffixed 'freewin' at the end of my @enabled-plugins, ... 
g.app.config.getEnabledPlugins()) now shows the other ones, with 'freewin' 
at the end, even though nothing has been installed for that and no 
z-open-window command is available. Is something cached here??

That seems a bizarre buglet, but I am not going to pursue it for now. I 
think I will submit a small PR with slight documentation clarification.

Anyway, I seem to be progressing, thanks...

    J^n


On Sunday, November 3, 2024 at 10:35:44 PM UTC [email protected] wrote:

> On Sunday, November 3, 2024 at 5:06:35 PM UTC-5 jkn wrote:
>
>
> The .pyc files in my plugins/ directory are extremely old, I am sure they 
> predate anything in myLeoSettings.leo ...
>
>
> All .pyc files with Python 3.x go into a *__pycache__* folder (I don't 
> know if this started with Python 3.0 or with a later version of 3.x). If 
> you have any that aren't, they might date back to Python 2 days.  Could 
> that really be?
>

-- 
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/4c66243d-67f7-4191-a7f9-325858f2aeeen%40googlegroups.com.

Reply via email to