Given that Apple is going to stop including Python in the next release of macOS (see the super annoying and fear inducing dialog box in Monterey), adding our own Python installation and migrating to Python 3 at the same time is one of the top priorities this year. This is a big task and will take much of our bandwidth. For Indigo scripters and plugin developers, a great way to start looking at the Python 3 migration is to read through
this Python 3 porting guide. There's a good bit that you can do now that's backwards compatible with Python 2.7 which will make your eventual migration much less painful.
Take this as your first warning:
Python 3 is coming likely around mid-year so if you are a plugin developer (or to a lesser extent scripter) you should start learning about Python 3 changes sooner rather than later. There aren't a big number of breaking changes going from Python 2.7 to Python 3, but enough that you are likely going to need to do some updates. We are currently planning on Python v3.9, but that may change to v3.10 depending on how solid/reliable that version appears to be closer to release. You probably want to avoid any 3.10 specific features until you hear otherwise from us.
The other top priority is getting the next Indigo Touch release out - we hope to have that done soon so we can turn our full attention to Python migration and inclusion.