Provided you’re not after anything more than tinker/hack then maybe. Reading code enough to understand why something is broken and being able to hack it to fix my problem is a whole different ball game to getting something up to the level for a PR that lands in PIP and who knows where else around the globe while not breaking other peoples usage…
The pyowm code structure wraps onecall up inside the broader weather API set. Openweathermap have not deprecated that (so /weather works at 2.5 while /onecall doesn’t) so it’s not even a case of updating the whole weather module to v3 and change it’s parsing code. One-call probably needs to be pulled out to a separate module as things like the pollution and agro APIs have been.
There is a ticket raised directly against pyowm but no response on that yet from the owner. Given they can undoubtably do a better job than me both knowing their code (let’s face it, Github isn’t the best place to find design docs, test approaches etc) and being a better Python user I’d rather give that route a chance.
Who knows though - maybe I’ll get bored next week at the out-laws…
Edit:
Curse you @nickrout ! My curiosity has gotten the better of me and it looks like pyowm may have a reasonable automated test setup so that’s one less excuse I have!