What a worthless semantic distinction. You don't want to be executing code to determine why an Exception occurred because you do not trust support devs to access all of the data in the production system.
"Exceptions happen" is true, but that's not satisfactory in an organization focused on quality. On Fri, Sep 25, 2020 at 5:38 PM Chris Angelico <ros...@gmail.com> wrote: > On Sat, Sep 26, 2020 at 7:25 AM Wes Turner <wes.tur...@gmail.com> wrote: > > > > (Executing arbitrary code on a production server is debugging in > production. > > > > Logging (additional information added to exceptions with 'raise _ from > _`) may assist with root cause analysis and debugging on a different > instance but IMHO logging is not debugging.) > > > > Uhh... okay.... sure. What if you add instrumentation to the live > server specifically so that it can log useful exceptions as you're > trying to probe a bug that shows up only in prod and only once every > two weeks? Is that debugging in prod, or is that logging? > > Or... does the distinction really even matter, and "debugging in prod" > is just part of life? > > ChrisA > _______________________________________________ > Python-ideas mailing list -- python-ideas@python.org > To unsubscribe send an email to python-ideas-le...@python.org > https://mail.python.org/mailman3/lists/python-ideas.python.org/ > Message archived at > https://mail.python.org/archives/list/python-ideas@python.org/message/THD4Y4RKERBSFUTU36EQHBEPDGTLIVQM/ > Code of Conduct: http://python.org/psf/codeofconduct/ >
_______________________________________________ Python-ideas mailing list -- python-ideas@python.org To unsubscribe send an email to python-ideas-le...@python.org https://mail.python.org/mailman3/lists/python-ideas.python.org/ Message archived at https://mail.python.org/archives/list/python-ideas@python.org/message/G3K55L2GFHP2R3PSTK5POM4E4BPZZH6P/ Code of Conduct: http://python.org/psf/codeofconduct/
