Of course, as I write this ansible is broken on one of my machines for reasons that appear to stem from a python 3.x->3.y update, so...
OTOH a script for /bin/sh written 30 years ago has a good chance running today unchanged.
Having said that, I still would not recommend shell for anything that needs to be robust and secure.
What was definitely problematic was the update from 2 to 3. Another problem may be dependency management (people not pinning dependencies). But the python itself? What does it even mean? Interpreter not starting?
Usually when I port shell scripts to python, I create a folder for it and throw in some setup.py / requirements.txt. But lately, I've automated most of the deb package creation process (https://copier.readthedocs.io), and I typically create the whole deb package. Of course, for single use stuff, I don't bother with either.