py3 is great, and it looks like it is the way to go for all new python stuff. but unfortunately supervisord, a process management system that we use) is explicitly stated as still not py3 compatible, which we already spent a fair amount of time on thus far. so this would pose some major issues in our trying to jump on the py2=>py3 bandwagon for new microservices.
however, it seems this may not be the right place to sort out this issue, as this particular situation is not one that that datawire ecosystem has needed to deal with :(
supervisordbut the docs reference DJB's daemontools which I'm familiar with. My thought on your py3 problem is that if you're writing a net-new microservice, you can build it in Py3, and adopt a different mechanism for
supervisordthat is Py3 compatible.