If you’re not confident/comfortable compiling your own Python from the tarball, then that sort of upgrade is probably best avoided until the Raspbian folks update Python in the distro.
But, FWIW, I found a simple sequence of steps that worked once you have later Python compiled and installed:
I created a new venv using the newer Python, copied HomeAssistant config over to it (I chose to keep my config inside the /srv/homeassistant folder, not in ~root/ or elsewhere), and everything is happy. I had feared the worst since not many people mentioned trying HAss under anything later than 3.6.x, but this instance of 94.x seems quite happy there.
Look at my link (6 posts above). I could get it updated in kind of 20 steps that are listed there. Take a look. I could not have done it by myself alone.
Getting a specific Python version in Linux is often doc’d well in myriad posts. The steps are pretty simple (as long as everything goes as intended). You’ll know if the compile fails - just stop there if not comfortable figuring out what’s missing.
But if you get the newer Py installed, then just follow the HA instructions for a new setup (I use Virtualenv) and your existing config will rule it.
I don’t know python either. The steps are pretty polished right now. Sure, a very basic knowledge of what you are doing is recommended. I advice you to do a backup first.
These instructions as provided by @anon34565116 have been confirmed to work by myself and others. They are specific to a Hass installation in a venv and were carried out on a Raspbian Stretch Lite OS on a Raspberry Pi 3.
They will download Python 3.7.3 source, build, compile install and replace your current venv w
I’ve no doubt this subject will be revisited as we come closer to Python 3.5 deprecation time. At least we now have a definitive set of instructions that will work on a Hass installation in a venv.
The crazy thing is, I mainly followed the script the Hassbian folks wrote but the HASS developers do not care enough to share with others who could use it.
OK. Yes me again.
Fearing breaking my working system I bought a new Pi3 B+ from Amazon to experiment on.
After setting it up, doing all the updates et al I went through ConcordeGE’s steps.
I got further but still failed at first.
Crawling through the messages I found it was missing a uuid include folder and the ffi headers/librarys so google found them as
sudo apt-get install uuid-dev libffi-dev
I redid the ./configure and the make and it claims to have worked.
I’ll put it on the working rig tomorrow.
Basically: Thank you to everybody who made suggestions.
Don’t you thinks the issue will simply go away when python is upgraded as part of the raspbian stretch distro? Hoping of course this will not be too far out.
