On 11/30/2014 12:18 AM, Steven D'Aprano wrote: > > Ah, wait, I see the reference. You're talking about the quote from James O > Coplien: > > "An even more professional approach is to leave the assertions > in the code when you ship, and to automatically file a bug report > on behalf of the end user and perhaps to try to re-start the > application every time an assertion fails." > > > Sounds reasonable to me (modulo privacy considerations). Many modern > software already does this: Firefox, Windows, KDE all have forms of crash > reporting that will automatically submit bug reports to the developers for > you. And Firefox at least will try (and generally succeed) to automatically > restart after a crash.
The error-catching/reporting/restarting framework is fine. My assertion (pun intended) is that building that framework on assert, which can be unknowingly disabled by the end-user, is foolish. -- ~Ethan~
signature.asc
Description: OpenPGP digital signature
-- https://mail.python.org/mailman/listinfo/python-list
