[jnbiche]

Sure, do that. I'm not a Python fanboy, and there were some issues with how the transition was handled. Move to another language if you have the manpower. I think in in this case, since they claim to not even have the manpower to do some relatively straight-forward migrations from Python 2 -> 3 and/or they have some dependencies on Python2, I'm doubtful that's even an option.

I'm just pointing out that it's a risky move to adopt a soon-to-be-deprecated programming language for new projects, given the potential for security issues that won't be patched. It's the kind of ignorant arrogance that has always bugged me about many companies with non-technical management (please note: these words are not directed at user kgrave given that this appears an edict from above at his company, and he's unable to change it).