| 6 Feb 2025 |
dotlambda | Otterwise we should revert the aiomqtt bump | 01:17:44 |
dotlambda | * Otterwise we should revert the aiomqtt bump or mark the package broken conditionally | 01:18:07 |
dotlambda | But putting a versioned attribute in the dependencies of a Python module is a bad idea | 01:18:28 |
@hexa:lossy.network | that was probably me though | 01:20:25 |
@hexa:lossy.network | and I do know better | 01:20:32 |
@hexa:lossy.network | I hate the paho-mqtt 2 migration | 01:20:44 |
@hexa:lossy.network | I'm not sure what direction is better at this point | 01:21:09 |
dotlambda | Are there any users outside of HA? | 01:23:07 |
@hexa:lossy.network | I have no idea | 01:24:22 |
dotlambda | Let's try moving to paho-mqtt_2 by default with the next python-updates | 01:48:22 |
dotlambda | Is there a HA issue about the migration? | 01:48:35 |
@hexa:lossy.network | not sure they have these kinds of issues | 01:50:09 |
dotlambda | https://github.com/home-assistant/core/pull/136130 | 01:51:42 |
@hexa:lossy.network | huh, ok | 01:53:18 |
@hexa:lossy.network | but yeah, it is usually someone doing a herculean effort | 01:53:29 |
@hexa:lossy.network | and we can probably just pick that as patch | 01:54:30 |
@hexa:lossy.network | if it isn't in the release | 01:54:39 |
@hexa:lossy.network | ah yeah, merged yesterday | 01:54:59 |
dotlambda | In reply to @hexa:lossy.network and we can probably just pick that as patch I don't think that's a good idea. Might inadvertently break things | 01:55:34 |
dotlambda | Let's wait till March | 01:55:40 |
@hexa:lossy.network | frankly, python-update cycles are nuts | 01:56:25 |
@hexa:lossy.network | too few people chiming in | 01:56:30 |
dotlambda | Sorry, I'm not helping either. Other priorities I guess :/ | 01:59:57 |
@hexa:lossy.network | yeah, I get that | 02:00:28 |
dotlambda | I'll make a PR for paho-mqtt v2 by default some time this week | 02:00:31 |
@hexa:lossy.network | the feedback cycles are much better than years ago | 02:00:43 |
dotlambda | Thanks for your herculean efforts with every python-updates cycle! | 02:01:23 |
@hexa:lossy.network | rebasing quickly to get rid of the llama failures hopefully | 02:04:22 |
@hexa:lossy.network | done | 02:07:39 |
@hexa:lossy.network | looks like we're not getting any CI | 02:10:32 |