On Thu, 11 Mar 2021 at 23:11, Ethan Furman <et...@stoneleaf.us> wrote: > Basically, you are looking at two different philosophies: > > - Always double check, get good error message when something fails > > vs > > - check during testing and QA, turn off double-checks for production for best > performance possible.
In a perfect world, I said the second option is the best. But for the majority of projects I contributed, speed was not a critical issue. On the contrary, it's very hard to get meaningful informations about problems in production, so I'm in favour of the first school :) -- https://mail.python.org/mailman/listinfo/python-list