lofty hornet
So during beta and now after the release, we see some issues where people have installed the new version and some dependencies don't support this, for example https://github.com/home-assistant/core/issues/164821.
I'm wondering if there are ways we can communicate this better so custom integrations can prepare. I don't believe we did much public communication around this.
Cc @strong sequoia @marsh loom
strong sequoia
It's written in the release docs that we have upgraded the Python version
so we communicated it already in the beta
lofty hornet
Yes, but can we be even more upfront than just a week?
strong sequoia
Python upgrade was done after the last beta cut. So it was more than a month out in the nightlies
lofty hornet
Sure, but I don't consider that communicated
Like I don't consider every custom component dev to run their dev env every week, or test their integration on nightlies
marsh loom
At least for the issue you've linked above, all that's needed seems to be a dependency bump in the custom integration: https://github.com/amol-/dukpy/releases/tag/0.5.1
strong sequoia
Sure, but I don't consider that communicated
what would you then consider?
I consider it as communicated if it is in the release notes
lofty hornet
Would it make sense to post a blogpost in the devblog about a new python version and when we expect to upgrade. Or maybe just post it when we know our own timeline
lofty hornet
I consider it as communicated if it is in the release notes
Yes, we communicate it, but I think it would be cool if we can be more upfront so people have time to prepare
Like, we also post devblog links in the release notes, the 2026.2 could've had a blog like "hey, we're going to switch to python 3.14, make sure you test in the coming month to avoid surprises"
lofty hornet
strong sequoia
<https://github.com/home-assistant/core/issues/164861>
Just out of curiosity why do you think thats Python 3.14 related?
full halo
Is the ADR at https://github.com/home-assistant/architecture/blob/master/adr/0020-minimum-supported-python-version.md stale then? I’m working on a custom integration and was intentionally tracking 3.13 to follow that. From what I can tell Python 3.15 isn’t out yet.
full halo
for myself, I read the update notes not as Home Assistant itself requiring Python 3.14, but that the HAOS / containers were updated to run on Python 3.14.
lofty hornet
Yea I think you have a point, the ADR wasn't followed and should likely be updated after the removal of core and supervised install methods
dusky eagle