> On 07-Jul-2015, at 8:39 pm, Cédric Krier <[email protected]> wrote: > > On 2015-07-07 07:34, Mariano Ramon wrote: >> >> >> On Monday, July 6, 2015 at 6:40:06 PM UTC-3, Cédric Krier wrote: >>> >>> On 2015-07-06 12:27, Mariano Ramon wrote: >>>> is there anyway to customize runtime errors that show the python >>> exception >>>> and use a catch all with a more user friendly message? >>> >>> By definition a traceback is an exception that is not expected. >>> Hiding it will just result of never fixing the problem, so that's why >>> Tryton shows such unexpected error. >>> If you want a friendly message, you must write code that doesn't crash >>> unexpectly. >>> >>> >> >> Of course, it was not intended as a solution. I asked because frameworks >> usually have a debug mode that works like it does now and the prodution >> mode where internals are not leaked in case of a bug. > > What will be leaked that is not already public? > Also it is the best way to have issue in production that you can not fix > because you don't know how to as you don't have the traceback.
Its about hiding the traceback from end user because he cannot understand it. I feel passing trace to softwares like sentry[1] helps you to debug it easily and you are not losing stack trace anyway :) [1] https://github.com/getsentry/sentry <https://github.com/getsentry/sentry> > > > -- > Cédric Krier - B2CK SPRL > Email/Jabber: [email protected] <mailto:[email protected]> > Tel: +32 472 54 46 59 > Website: http://www.b2ck.com/ <http://www.b2ck.com/>
signature.asc
Description: Message signed with OpenPGP using GPGMail
