The future of hbmqtt? Is it still maintained or EOL? about hbmqtt

[FlorianLudwig]

hbmqtt has been forked

The fork is called amqtt, github project here: https://github.com/Yakifo/amqtt

Changes include:

• Python 3.8 and 3.9 support
• Works with current websockets package
• Overview of merge requests integrated from hbmqtt can be found here: Yakifo/amqtt#7

[HerrMuellerluedenscheid]

Hi @njouanin, thanks for the info. good to know! I agree with @FlorianLudwig. It would save a lot of confusion and extra work to keep the pypi package maintained. Also, if people install unmaintained software can cause significant security risks.
Me and a colleague would be happy to start a more community driven support for hbmqtt. Anybody else interested, feel free to drop a message.

[njouanin]

Hi, I'm not maintaining this repo anymore. Please feel free to fork.

[FlorianLudwig]

@njouanin thank you for the heads-up.

Would you be willing to turn over the pypi package to a group of volunteers to maintain it?

[HerrMuellerluedenscheid]

ping @njouanin

[shipmints]

https://github.com/M-o-a-T/distmqtt is a fork that's been updated a bit (and you have to prefer anyio vs. asyncio). However, a quick reading shows that it has the same issues as in #237 but if it is more likely to be repaired and to accept contributions it may be time to either fork hbmqtt itself with proposed changes and corrections (and with more comprehensive tests) or look at someone else's fork. I'd hate to abandon @njouanin after all the work put into hbmqtt, and he may have an interesting backlog of work and ideas. When hbmqtt is used with the features that are known to work, staying away from those that break ala #237, and using the most recent release that incorporates key fixes, it works fine for low message-rate applications. I value a pure-python implementation using as few extra dependencies as possible that is easy to reason about.

[shipmints]

@HerrMuellerluedenscheid, I'll try to lend a hand.

[shipmints]

@HerrMuellerluedenscheid not sure how quickly you want to address this. Let me know. I suppose that until @njouanin helps with an ownership transition of the existing pypi package or we elect to replace it with a new one, this initiative will be stalled.

[pavandv]

@HerrMuellerluedenscheid count me in