Thanks for the quick feedback. Also tested calling weewxd from outside of the venv via a full path ala > ~/weewx_venv/bin/weewxd which I suppose is where a future systemd startup > file use if an absolute path was specified (???) >
Yes, exactly so. You don't need to 'activate' the virtual environment --- all that does is put it in your PATH. If you already have an explicit, absolute path to weewxd, that's good enough Re: your installer mechanisms options, I lean toward this way since it > relies on just core python and not a third party wrapper tool that might > theoretically go away someday or might not work on all the unusual/creative > places folks run weewx on like NAS or under WSL and the like. > I just worry about the multiple steps involved and a newbie's ability to do them. In any case, any of the ways I outlined in the "pip" document will work, it's just that I'd like to settle on one "official" way that we document and encourage users to use. For the future, I guess I'd like to also see docs re: how to upgrade weewx > and/or switch to a specified version of weewx. Sometimes folks need/want > to freeze to a particular version. > One nice feature about pip is that you can install a specific version. For example *pip install weewx==5.1.3* So many docs, so little time... -tk -- You received this message because you are subscribed to the Google Groups "weewx-development" group. To unsubscribe from this group and stop receiving emails from it, send an email to weewx-development+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-development/CAPq0zEBEAyzM%3Dnb6EqHHKWOvzb4Rs-K_5Uy1-9D%2B8iD6ybPtGg%40mail.gmail.com.
