use ‘python3 -m venv ~/venv’ to create the environment in ~/venv. then in your shell run ’source ~/venv/bin/activate’ to set up the shell environment (initialised python bindary, PYTHONPATH etc). i put this in my ~/.bashrc
a key trick is that running the initialised python binary (~/venv/bin/python3) on its own sucks in the environment - really, really handy in systemctl unit files ⊣GE⊢ > On 25 Aug 2023, at 10:41 am, vince <vinceska...@gmail.com> wrote: > > For the venv you do a 'source weewx-venv/bin/activate' then do a pip install > to add modules within the venv. All you have to remember is to activate the > venv before running weectl, as well as read the docs for the new syntax for > doing things. It's pretty easy to pick up. > > systemctl works fine. Just go with it :-) -- 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 weewx-user+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/AB60763A-9EF8-4C4A-B870-2300896D0768%40geddy.au.
