Re: [weewx-development] config file quoting and whitespace changes during upgrade

Everything I’ve wanted to do in weeex.conf and skin.conf could only be done via a text editor. The current ini format (or toml format) is much easier to edit than json or yaml.For example: I’ve been writing an Alexa skill to use data that Weewx writes out - among other things - to announce weather

Re: [weewx-development] config file quoting and whitespace changes during upgrade

On Sunday, November 6, 2022 at 3:52:07 PM UTC-8 Greg Troxel wrote: > Regarding setup/wizards, I don't think there is anything wrong with > having a program that you run and asks questions or whatever and then > outputs a new weewx.conf in the current directory. The user can then > put it in $pr

Re: [weewx-development] config file quoting and whitespace changes during upgrade

On Sunday, November 6, 2022 at 3:39:54 PM UTC-8 Tom Keffer wrote: > One of the things I disliked about wview was its many configuration files > and then, later, its database-oriented configuration. I wanted everything > in one, easily readable, place. > > To do edits of the config file it's best

Re: [weewx-development] config file quoting and whitespace changes during upgrade

Tom Keffer writes: > I hear you on the complexity of Python packaging. I've been using node for > a few years now and they have done a much better job. Unfortunately, the > Python gods have decided to create a backend standard (PEP 517 > ), and then rely on a 3

Re: [weewx-development] config file quoting and whitespace changes during upgrade

Tom Keffer writes: > The problem is not the configobj format, it's the future readonly nature of > Python installs. The config file (and skins) are considered "data", and the > only way to include "data'' is within a Python package. That package might > be in a zipfile or Python egg, hence its r

Re: [weewx-development] config file quoting and whitespace changes during upgrade

One of the things I disliked about wview was its many configuration files and then, later, its database-oriented configuration. I wanted everything in one, easily readable, place. To do edits of the config file it's best to read it in using configobj, do the edits in Python, then write it back out

Re: [weewx-development] config file quoting and whitespace changes during upgrade

On Sunday, November 6, 2022 at 2:07:07 PM UTC-8 Tom Keffer wrote: > The thinking is that the config file, skins, and database would all be > initialized on first use, using the supplied readonly data as templates. > The problem is that it's hard to get weewxd going without doing some > customiz

Re: [weewx-development] config file quoting and whitespace changes during upgrade

Joel, thanks for that link. Meson looks interesting. I'll check it out. On Sun, Nov 6, 2022 at 3:00 PM Joel Bion wrote: > ..there's also this interesting page: > https://whynothugo.nl/journal/2022/07/26/meson-for-python-applications/ > > On Sun, Nov 6, 2022 at 2:57 PM Joel Bion wrote: > >> I've

Re: [weewx-development] config file quoting and whitespace changes during upgrade

..there's also this interesting page: https://whynothugo.nl/journal/2022/07/26/meson-for-python-applications/ On Sun, Nov 6, 2022 at 2:57 PM Joel Bion wrote: > I've been wondering about the big changeover that will occur with Python > 3.12 (the removal of distutils). I use three packages that ar

Re: [weewx-development] config file quoting and whitespace changes during upgrade

I've been wondering about the big changeover that will occur with Python 3.12 (the removal of distutils). I use three packages that are Python applications that need to configure things at a system level: fail2ban, ufw, weewx. On the ufw git site, this page has a rather interesting conversation go

Re: [weewx-development] config file quoting and whitespace changes during upgrade

Doug: Yes: you'd either install using pip, or a package installer (apt, yum, etc.). I'd sure like to get out of the business of custom installs and, instead, rely on Python tools and all their goodness. Vince: The thinking is that the config file, skins, and database would all be initialized on fi

Re: [weewx-development] config file quoting and whitespace changes during upgrade

Wow if you drill down through that thread it gets crazy confusingbut (this one) does help a little although (this other one)

Re: [weewx-development] config file quoting and whitespace changes during upgrade

Yes, this would be for V5. Most likely Python 2.7 would be dropped. The problem is not the configobj format, it's the future readonly nature of Python installs. The config file (and skins) are considered "data", and the only way to include "data'' is within a Python package. That package might be

Re: [weewx-development] config file quoting and whitespace changes during upgrade

If there’s a new format, I’d much prefer TOML vs. JSON/YAML. TOML makes some improvements over ini files, without being an easy-for-humans-to-make-mistakes format like JSON.But it sounds like the issue is more fundamental- that the issue has something to do with the new Python package installer not

Re: [weewx-development] config file quoting and whitespace changes during upgrade

This one scares me, as previous versions have definitely tweaked the contents along the way of the upgrade path from version to version. Is this something for a future 5.x major version that might have breaking changes like dropping python2 support or the like ? Has there been any thought to

Re: [weewx-development] config file quoting and whitespace changes during upgrade

Yes, all the time. Semantically, 'configobj' does a round trip, but textually, it leaves much to desire. Going forward, the intention is to start treating weewx.conf as "readonly". The installer will not try to "update" it, not even to change the version number. Any changes would be up to you, pe

Re: [weewx-development] config file quoting and whitespace changes during upgrade

I’ve also noticed this. Sent from my iPhone > On Nov 6, 2022, at 4:55 AM, Greg Troxel wrote: > >  > (I have been running WeeWX since the very end of 2017, and updated a few > times. I'm building with setup.py on NetBSD, but I'm quite used to python.) > > There is some config file auto updat

Re: [weewx-development] How about a length property in TimespanBinder?

Tom Keffer schrieb am Samstag, 5. November 2022 um 13:12:28 UTC+1: > Good idea. Wouid you like to submit a PR? > >> >> Here you are: https://github.com/weewx/weewx/pull/809 -- You received this message because you are subscribed to the Google Groups "weewx-development" group. To unsubscribe fr

[weewx-development] config file quoting and whitespace changes during upgrade

(I have been running WeeWX since the very end of 2017, and updated a few times. I'm building with setup.py on NetBSD, but I'm quite used to python.) There is some config file auto update/merge stuff. My usual practice is to keep my config file matching the default example in the source code, e

Re: [weewx-development] How about a length property in TimespanBinder?

jpb...@gmail.com schrieb am Samstag, 5. November 2022 um 13:17:01 UTC+1: > I love the idea but can it be called something more specific to time? > (Such as “duration”?) > As there are no further comments I guess I will send the PR as shown in the first post. -- You received this message beca