Yes. I misspoke earlier. It would be nice to keep the 'upgrade' option around too since those items tend to change a little as well from version to version and it does provide a nice way to catch up to those changes if desired. Now whether it's required all the time, that's perhaps a different story.
(FWIW - you might want to push the current docs up to weewx.com when you get a chance. What's there is a little dated.) On Sunday, February 19, 2023 at 6:24:14 PM UTC-8 Tom Keffer wrote: > That's a different command: "weectl station upgrade-skins". > > > > On Sun, Feb 19, 2023 at 12:21 PM Vince Skahan <[email protected]> wrote: > >> Isn't having 'upgrade' a good thing for the case where folks want to >> upgrade the core skins to the newer version ? >> >> On Sunday, February 19, 2023 at 5:06:55 AM UTC-8 Tom Keffer wrote: >> >>> I suppose we could not introduce `weectl station upgrade` until it's >>> needed. >>> >>> On Sun, Feb 19, 2023 at 4:53 AM matthew wall <[email protected]> wrote: >>> >>>> > On Saturday, February 18, 2023 at 1:24:47 PM UTC-5 [email protected] >>>> wrote: >>>> > On Saturday, February 18, 2023 at 5:49:11 AM UTC-8 Tom Keffer wrote: >>>> > ... with the upcoming Version 5: you can reinstall with pip as many >>>> times as you want. Just don't >>>> > run "weectl station upgrade" afterwards. >>>> > >>>> > Confused. >>>> > I thought you 'always' needed to run "weectl station upgrade" after a >>>> v5 pip install so that the data >>>> > directory always lines up with what pip installed into the code >>>> directory. >>>> >>>> the intent is that a user should *never* have to run 'weectl station >>>> upgrade' >>>> >>>> as long as weewx remains backward-compatible, the only time you should >>>> have to upgrade your configuration is (1) when a non-backward-compatible >>>> change is introduced (signaled by a major version number change), (2) when >>>> a new feature is introduced that requires some non-default configuration >>>> (e.g., if you want to update a skin), or (3) if you want your config to >>>> contain the latest syntax/naming/conventions with no older patterns that >>>> require backward-compatibliity from the weewx codebase. >>>> >>>> -- >>>> 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 [email protected]. >>>> >>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/weewx-development/26942509-a85b-46b3-8d44-71ba329c811fn%40googlegroups.com >>>> >>>> <https://groups.google.com/d/msgid/weewx-development/26942509-a85b-46b3-8d44-71ba329c811fn%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> >>> -- >> 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 [email protected]. >> > To view this discussion on the web visit >> https://groups.google.com/d/msgid/weewx-development/9ecbf21a-a008-4067-8bb1-5b2b69680018n%40googlegroups.com >> >> <https://groups.google.com/d/msgid/weewx-development/9ecbf21a-a008-4067-8bb1-5b2b69680018n%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-development/17850fbe-5a37-4b51-a16c-c126e38311b9n%40googlegroups.com.
