I believe that forward compatibility is a lot more important than backward compatibility, because you're never gonna transition to the past.

We do try to keep up with the latest python releases but we do need to try to keep things stable and not bleeding edge to maintain production quality and user experience.

@forslund

We do try to keep up with the latest python releases but we do need to try to keep things stable and not bleeding edge to maintain production quality and user experience.

I see. just merge it.

I did an almost clean install on Debian 10, and it seems to be working fine.

I see 20.0.1 got released after this PR was made, should we bump straight to that?
Once we confirm the version to update to I'll test it across all platforms.

Also, this is outside scope of this change, however:
I left my Skills directory in place but because I was working from a fresh venv many Skill dependencies weren't installed. Wondering if we should be checking Skill requirements in case it is a "re-installation" rather than completely fresh install?

@opensource-assist it is tempting to just update everything to the latest version, but a lot of people use Mycroft on a daily basis and they understandably would get pretty frustrated if everything stops working because we haven't taken the time to test things properly. The good thing about open source is that you are free to fork it and run everything on the bleeding edge :)

I'll update to 20.0.1 and see that it works.

There are (or at least were) a check in msm to "re-pip" (as it was known) on updates if a new venv is in place. Possibly dev_setup.sh should remove the .msm file to directly trigger an update or maybe dev_setup should run a msm update?

@krisgesling switched it to 20.0.1 seems to be working just as well...

Bumped it one more time to 20.0.2 lets hope it's stable now.

20.0.2 is also working fine for me

Then let's merge this :)