Re: [weewx-development] Abridged summary of weewx-development@googlegroups.com - 1 update in 1 topic

[Steven Sheeley]

Having created a python script to do that for both the weather34, and DivumWX skins, to add in thier stanzas to weewx.conf, it can be a stone cold princess, specially when you take a look at what someone can do to thier weewx.conf when armed with a text editor.  TBH, your mileage will vary, I think it's nice to have but.........

On 26/02/26 10:01, weewx-de...@googlegroups.com wrote:

weewx-de...@googlegroups.com

Google Groups

Today's topic summary
View all topics

• complete editability of weewx.conf - 1 Update

complete editability of weewx.conf

Vince Skahan <vince...@gmail.com>: Feb 25 10:10AM -0800 Would some kind of utility to permit simple edits of 'any' item in weewx.conf be of any value to think about ?   Something like "weectl edit config" or the like (for discussion purposes) ? ...more

Back to top

You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page. To unsubscribe from this group and stop receiving emails from it send an email to weewx-developm...@googlegroups.com.

[Joel Bion]

I look at it this way: the installation process should set the “official” level of difficulty to use a product. From my understanding, to install WeeWX requires:

1) Knowing how to install a Python package.

2) Editing WeeWX.conf to set at least the station type.

3) Possibly using weectl to set up parameters.

4) possibly further editing WeeWX.conf 

I don’t think, after doing all the things described above, using an editor for stuff after initial install is a stretch for those who use WeeWX.

Yes, mistakes can be made. I certainly believe add on packages to WeeWX should add in their default values for additions they give to the conf file.

But have WeeWX users struggled with config file editing?

[last thought]

[[topictoopineabout]]

Nested-parameters

[[[opinion]]]

Are a bit unsightly

[[[however-clause]]]

Can’t think of a better way to do them given this file format

On Feb 25, 2026, at 10:36 PM, Steven Sheeley <steven....@gmail.com> wrote:



--
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-developm...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/weewx-development/a266dcc7-78b2-40cf-82ba-5eaa922bb841%40gmail.com.

[Tom Keffer]

I admit that configobj isn't perfect, but it was the best available back in 2008.

The biggest problem is not so much the deep [[[[nesting]]]] that is required per se, as that it's not block structured. This comes into play when overriding skin.conf settings in weewx.conf. The user has to consciously add the correct number of brackets.

If I was writing WeeWX today, I would definitely look at TOML (as implemented by tomlkit).

To view this discussion visit https://groups.google.com/d/msgid/weewx-development/A82FC015-8C75-4548-99A5-CA3A0423FD56%40gmail.com.

[Vince Skahan]

If weewx does not switch to TOM(L) there is no justice here for all your years of work :-)