On Tuesday, November 8, 2022 at 10:02:26 AM UTC-8 Tom Keffer wrote: > 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. >
Sure - just throwing it out there if an 'assemble from pieces' kind of thing is worth anything to think about investigating. Perhaps that is sidetracking things a bit anyway. Sorry. Could you explain what your second paragraph means in layman's terms because I'm obviously not getting it. - if setup.py can only move code into place as step one - then why can't a new second step's tool 'not' using setup.py do whatever setup.py will not let you do ? - and then start up like we do now So a 'build install startup' scenario becomes a 'build install configure startup' future. One more step. Is it really more complicated than that ? -- 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/d123f83e-5f26-4ea0-be12-cb62151bf9bdn%40googlegroups.com.
