Hrm. Thanks for the link... probably not going to end up being a Django issue. I will report back if it is.
On Sunday, April 12, 2020 at 10:25:07 AM UTC-4, Tim Graham wrote: > > The relevant commit might be > https://github.com/django/django/commit/10b44e45256ddda4258ae032b8d4725a3e3284e6. > > That change was made in Django 2.1. You didn't say what version of Django > you're using. > > You'll have to give more details about your case and what's behaving > differently. > > On Sunday, April 12, 2020 at 8:57:12 AM UTC-4, Gordon wrote: >> >> Why was the error log removed from handle_uncaught_exception? I didn't >> find mention about it but I've recently encountered a middleware causing a >> 500 error and not getting a traceback log was unexpected. >> >> >> https://github.com/django/django/blob/stable/2.0.x/django/core/handlers/exception.py#L115 >> >> Should it be added back or is it intentionally removed? >> > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/26ae2557-0035-4a26-99a6-c84d010604ee%40googlegroups.com.
