Using venvs won't help Python 3.13 find modules to use when they have only been installed for Python 3.11 to use.Interesting. But I though the entire point of (mandatory) venvs was to avoid this sort of issue. Or am I wrong?On a hunch, I changed the name of the Python folder within the venv's lib folder from python3.11 to python3.13 ...
If you want to use Python 3.11 you need to install the modules for 3.11
If you want to use Python 3.13 you need to install the modules for 3.13
If you want to use both you need to install modules for both 3.11 and 3.13 separately.
Each Python will only use modules installed for it or modules installed for any Python to use. Switch Pythons and each will only use the modules installed and available for it - That's venvs working properly as I see it.
I can't criticise hacking the names of folders to make things work but that suggests what has been done isn't being done in the correct way. I am not entirely sure what the correct way would be but it feels to me like Python 3.13 should have been activated, then the 'mariadb' module should have been installed for 3.13. Then everything should have just worked.
Forgive me if I am wrong but my reading of it is that Python 3.13 was activated and was expected to work with 3.11 modules which it won't. Then folder names were hacked rather than installing the module for 3.13.
Installing 'weewx' with Python 3.13 active should deliver a 'weewx' for 3.13 use with all the sub-folders named to be usable with Python 3.13. But I haven't tried it.
Statistics: Posted by hippy — Sat Aug 23, 2025 2:23 pm