jolly scroll
We currently have a constraint on setuptools < 82.0.0 because it doesn't contain pkg_resources anymore
This affects just two core integrations: neato and pilight
neato is resolved via https://github.com/home-assistant/core/pull/167758pilight has not been updated in 6 years https://github.com/DavidLP/pilight and has only 4 users https://www.home-assistant.io/integrations/pilightShould it be deprecated?
mint tulip
Yes
magic pier
In theory the RF platform should be able to replace pilight too... but that will probably still take a bit of time
mint tulip
Yeah but we shouldn't wait for it. We have axed old integrations before
Start by disabling it in manifest
jolly scroll
magic pier
I'm trying to understand when to disable and when to remove entirely. Is the idea here to 'call for maintainers' to pick this up? I.e. this breaks with version 2026.5, someone thinks 'I really need this though' and fixes the issues? Or is there another reason?
mint tulip
Oh right now we just delayed that discussion 😅 to move forward
I think we can remove it and no one has forked the library, no one probably cares
jolly scroll
There are four users, according to analytics
It's not much, but it's not zero
With zero users, I would have removed, but this gives opportunity for someone to pick it up
magic pier
But it's a bit weird to me that disabling is effective immediately (as far as I understand, this prevents HA from setting it up entirely?) while deprecation is usually done over a 6 month period with a repair issue warning users.
I guess the idea with disabling rather than removal is to allow for another person to step in and fix it without having to start from fresh. That makes sense. But we should give the user a bit of time to do that, don't you think? Like a month at least, ideally 6 months.