Before going down this path, I suggest you pick up and read The Mythical Man-Month. The experience the author has closely matches my own experience. What you’r

Before going down this path, I suggest you pick up and read The Mythical Man-Month. The experience the author has closely matches my own experience. What you’re describing has very little to do with python and a ton to do with your software developers and your environment. If you have bugs that are not caught before you reach production, how is your testing? Do you have a good level of unit test converge which can easily catch type safety issues? Do you have integration test and regression tests? As the mythical man-month states there is no silver bullet. No change in language will solve any significant portion of issues without further changes to your process. Nor will it increase productivity in any significant way. It also mentioned the theory of irreducible numbers of bugs. Changing languages will change where you see bugs but not the number or severity of the bugs. Of course you also have the second system effect which can be quite interesting. It basically states you’ll have many of the similar issues from your first system but also a bunch of new ones from your second. So what do you do? All is not lost. I would focus on making small but meaningful changes within your current team and environment. You’ll find the most long term success there. Going with a new language is new and exciting but it’s also extremely risky.