Because (1) its inevitable and (2) I’ll get tired of typing the wiki url explaining this. I just hope they wait long enough (that 1.x is gone) before removing the other signatures that have changed…
On Sunday 11 February 2024 at 14:23:07 UTC-5 vince wrote: > Why not stick with 1.6.1 indefinitely and the matching version of the > extension and not sweat it ? > > On Sunday, February 11, 2024 at 11:12:32 AM UTC-8 Greg Troxel wrote: > >> "bell...@gmail.com" <bell...@gmail.com> writes: >> >> > It currently will not work with paho mqtt 2.0.0 or higher. >> >> Sorry, I understood that. I have looked briefly at the migration which >> says "change your code because a function signature changed", and have I >> have been holding off because I'll need to fully absorb it, and then >> update rtl_433_mqtt_relay.pt (for which I am somewhat the maintainer) >> and a program (that I haven't published yet) that polls ups-nut and >> reports status over mqtt. >> >> What I meant, is, do you expect that when you figure out how to deal >> with the incompatible changes, you'll end up with a MQTTSubscribe that >> can function with either, or if we'll need to match versions. >> >> If there's a way to do it (try/catch and figure out the signature?) then >> presumaly the MQTT publish extension, rtl_433_mqtt_relay and everything >> else can use that technique. >> > -- 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 weewx-user+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/e1c26ae9-7e8a-4a89-bb81-d74e2a510306n%40googlegroups.com.
