Sorry, Vince, but I don't like your one file = one option approach. There would be dozens of files --- impossible to support.
Also, we cannot use setup.py() in an imperative approach any longer. No modifications of weewx.conf, or any other file. All you can do with the new setuptools is move things into place. Everything is declarative. No running of code. On Tue, Nov 8, 2022 at 9:56 AM Vince Skahan <[email protected]> wrote: > On Tuesday, November 8, 2022 at 9:48:43 AM UTC-8 Vince Skahan wrote: > >> what if you built weewx.conf at 'runtime' based on multiple >> mostly-optional config definitions.... >> > > Or if you didn't like doing it at weewx startup, hook it into './setup.py > build' or whatever that evolves to be. Same idea. Assemble weewx.conf > from pieces of the puzzle that are easier to add/delete/edit. > Service/extension authors might even be able to add asking questions to > their installation steps to preseed answers. > > > -- > 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/50d51375-8cf6-41cd-a8ff-d0038f586344n%40googlegroups.com > <https://groups.google.com/d/msgid/weewx-development/50d51375-8cf6-41cd-a8ff-d0038f586344n%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/CAPq0zEBxkAHkzX7mBtGJX58V9dUPX3EL5mTpSYtL0Joqcz3C9w%40mail.gmail.com.
