Vince Skahan <[email protected]> writes: > You generally can't avoid venvs on a modern python on a current os. Nobody > here did that. The python project forced that on everybody.
That's not strictly true. pkgsrc has packages for a vast number of py-foo all installed in the system site-packages, and it works fine. I am actually running weewx that way, with the weewx code in /usr/pkg/lib/python3.13/site-packages/weewx and so on. In my case, the weewx progarm files are owned by root and live in the system. I am running it in a data directory (with config file and database) that is owned by a non-root user. Stepping back from weewx and python, this is totally normal, to use installed programs with your own data. <rant> I find that venvs are required because python culture says it is ok to have requirements as foo==x.y.z, rather than foo>=x.y. Thus, there is no way to have everything needed installed, and python packages with unreasonably specific dependencies (Home Assistant) have to be in a venv for isolation. The root cause of pinned deps, besides people thinking it is ok, is API instability within modules. </rant> -- You received this message because you are subscribed to the Google Groups "weewx-user" 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/weewx-user/rmipl5eumuo.fsf%40s1.lexort.com.
