One other thought, have you considered adding the functions from air_conf.py to your airQ driver file? Not that I had any wee_database like actions to include, but when I wrote the GW1000 driver I added numerous actions (mainly displaying GW100 config data) that could be selected when the driver was run directly. So in the end the user could run the driver directly and test the driver as normal, but they could also select various other command line options to perform various other related functions. This approach can bulk out your driver file but it has the advantage of putting everything in one place with the user only needing to use one command (with various command line options). If interested the relevant section of the GW1000 driver can be found on Github here <https://github.com/gjr80/weewx-gw1000/blob/master/bin/user/gw1000.py#L5673> .
Gary On Tuesday, 20 July 2021 at 19:48:30 UTC+10 kk44...@gmail.com wrote: > Ok. Thank you for your reply and explanation. > > gjr80 schrieb am Dienstag, 20. Juli 2021 um 10:30:10 UTC+2: > >> From the Zen of Python >> <https://www.python.org/dev/peps/pep-0020/#the-zen-of-python> ‘Simple is >> better than complex.’ >> > That's why I put the script into the same directory as wee_database, as it > has a similar purpose and a similar way of use. > > But considering your explanation, I will move the Python part of the > script into the user directory. And I will re-think how I can make the user > find it. > > >> >> > -- 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/fa5234a2-c8a4-4aca-9e74-2b3dd7b37a96n%40googlegroups.com.
