no idea, why to check the version here, but I doubt, that reading the 
readme file will proof the version required.
I had a look into the python3 packaging doc, where the correct version 
check looks like

from packaging.version import Version, parse

So, I think, that this should replace distutils in the future, if version 
check is needed. Anyway, I am not an expert. So, I trust in your coding.

Thanks
Peter
Jacques Terrettaz schrieb am Mittwoch, 11. Februar 2026 um 15:05:49 UTC+1:

> I removed weewx version checking, so no more need to import "distutils".
>
> It is now specified in the readme file that Weewx V3,8,0 or greater is 
> required.
>
> Le 11 févr. 2026 à 12:12, Vetti52 <[email protected]> a écrit :
>
> Great! Thanks a lot. 
> Just another question to your fork of M Wall‘s version: This one needed to 
> install python3-setuptools, because of a deprecated module „distutils“ used 
> here. Did you „repair“ this part? 
> Sorry for questioning, but I am completely naive with python.
>
> [email protected] schrieb am Mittwoch, 11. Februar 2026 um 11:31:24 
> UTC+1:
>
>> I have modified the original Windy uploader  to the Windy API V2 :
>>
>> https://github.com/Jterrettaz/weewx-windy
>>
>> Two parameters are required : station_id and station_password.  You can 
>> find these parameters here : https://stations.windy.com/stations
>>
>>
>>
>> Le mercredi 11 février 2026 à 10:56:57 UTC+1, Vetti52 a écrit :
>>
>>> Thanks for this information. Fortunately the old version works still 
>>> fine for me.
>>> Looking at https://stations.windy.com/api-reference, there is a 
>>> deadline:
>>> ______________
>>>
>>> This is a new API, effective from January 2026.
>>>
>>> If you are currently using a previous (legacy) version of the API, 
>>> please note that it is no longer supported. The legacy API will remain 
>>> operational only until the end of 2026, after which it will be fully shut 
>>> down.
>>>
>>> We strongly recommend migrating to the new API specification below as 
>>> soon as possible.
>>>
>>>
>>>
>>>
>>>
>>> *Observations*
>>> Upload measurements or read observations from your stations. 
>>> Authenticate with the station password.
>>> ______
>>> So there is no Api-Key needed for uploading data, but for management of 
>>> the station. 
>>> The station password is provided by Windy. If I would have a hint of 
>>> python skills, I would try to update the weewx windy uploader. Maybe 
>>> someone can do this until end of 2026, please????
>>>
>>> Kind regards
>>> Peter
>>>
>>> Tomasz J schrieb am Dienstag, 10. Februar 2026 um 19:10:17 UTC+1:
>>>
>>>> Hi all,
>>>> maybe I missed an announcement or update, but has there been any work 
>>>> on adapting the original Windy REST uploader for the new Windy Stations 
>>>> API 
>>>> v2?
>>>>
>>>> It looks like the legacy Windy uploader (API key–based) started 
>>>> returning HTTP 400 errors recently, likely due to Windy enforcing the v2 
>>>> endpoints and authentication model (station password / bearer auth).
>>>>
>>>> Is there an updated plugin or patch in progress, or are people handling 
>>>> Windy uploads via external scripts now?
>>>>
>>>> Thanks for any insight.
>>>>
>>>>
> -- 
> You received this message because you are subscribed to a topic in the 
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/weewx-user/-8W4t9NXiPA/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> [email protected].
>
> To view this discussion visit 
> https://groups.google.com/d/msgid/weewx-user/0f191852-dcfb-45fc-8b27-7bbd2f9045c1n%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/weewx-user/0f191852-dcfb-45fc-8b27-7bbd2f9045c1n%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion visit 
https://groups.google.com/d/msgid/weewx-user/5f79db6c-227f-4e82-8f8b-ba179ecabcf3n%40googlegroups.com.

Reply via email to