-
-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEAT] Update python to 3.12 #95
Comments
This is not a simple task. Our wheel builder is not set up for python versions out of cadence with the base OS and alpine does not have py 3.12 released yet (not even in their edge repo). It's a bold move to stay that close to cutting edge but the upstream project has vertical integration so they probably can afford the risk. It's a lot more trouble than it's worth for us. |
Are you sure you're using our image? We don't have a build for 2024.2 as it has not been released to stable yet. Latest we pushed is 2024.1.6 |
I use your git to build it with the beta. |
@florie1706 |
Hi @aptalca thanks for test build. Seems to work. Core integrations and some of my custom integrations worked. HA is running, no more warning (of course). But I needed to revert back because a couple of my custom integrations stopped working. I think they have to be upgraded to py3.12 as well. I check with the non working to get them run :) |
Hi, same Problem here: 2024.2.0 Frontend 20240207.0 original error message (in german): build_version | Linuxserver.io version:- 2024.2.0-ls229 Build-date:- 2024-02-07T21:02:11+00:00 |
Everybody will have this message because everybody uses the same image ;) You could also try the test build from @aptalca two messages prior yours or wait until python 3.12 is officially in the release images here. For now I would say it is just sort of a warning without any downside. Should be fixed until the 2024.4 release where python 3.12 will be mandatory. |
I use unraid, so I have no option but to just install from the community app store - which now does not work. |
Currently you need to roll back to the previous version and not update. |
Well thats a pain. Just restored - back to yesterday morning backups........ And now it starts - but no sensors are working at all - all offline..... I only moved to container from my VM 3 weeks ago and was stable on VM for years. |
Actually - my dashboard was like that - there are no actual sensors there are at all after restore!!!!!! |
But are your problems really related to my feature request to have python 3.12 in an upcoming release image? |
Prob not - I will have to work through the restores and manual copy - I am on holiday in bali - shold never have hit that update button while I am still 3 weeks away! |
Its fubar'd - I am going to have to set it all back up when I get back to Australia!!!!! |
Hi, also got the warning but I'm confused people already got issues cause the warning is just saying its going to break at version 2024.4. Anyhow I'm happy that the python upgrade to 3.12 got adressed cause like others here I'm also using unraid for some small instances of HA and I don't want to switch to anywhere else, Thanks. |
I currently using the 3.12 branch. it seems everything is working fine. |
@aptalca I used your test build from the beginning and with HA 2024.2.1 I built my own image which runs also very well. Nothing to report. Thanks again for your effort. |
Is this a new feature request?
Wanted change
Could you please be so kind to update python to the latest version :) Thanks in advance
Reason for change
As of Home Assistant 2024.2 I get an warning for this:
2024-02-01 09:35:46.392 WARNING (MainThread) [homeassistant.bootstrap] Support for the running Python version 3.11.6 is deprecated and will be removed in Home Assistant 2024.4; Please upgrade Python to 3.12
Proposed code change
No response
The text was updated successfully, but these errors were encountered: