3 ¯ôÁgÞã@s0ddlZddlmZejƒZde_ddd„ZdS)éN)Ú WSGIHandleréôcCs~y.t|jjjjdƒtƒr |t_n tjr,tj}Wntk rBYnXz*|dkrT|ƒ}|j |k rh|j |ƒ‚|‚Wdd}d}XdS)a¿ Alternative function for django.views.debug.technical_500_response. Django's convert_exception_to_response() wrapper is called on each 'Middleware' object to avoid leaking exceptions. If an uncaught exception is raised, the wrapper calls technical_500_response() to create a response for django's debug view. Runserver_plus overrides the django debug view's technical_500_response() function to allow for an enhanced WSGI debugger view to be displayed. However, because Django calls convert_exception_to_response() on each object in the stack of Middleware objects, re-raising an error quickly pollutes the traceback displayed. Runserver_plus only needs needs traceback frames relevant to WSGIHandler Middleware objects, so only store the traceback if it is for a WSGIHandler. If an exception is not raised here, Django eventually throws an error for not getting a valid response object for its debug view. ÚselfN) Ú isinstanceÚtb_nextÚtb_frameÚf_localsÚgetrÚtldÚwsgi_tbÚAttributeErrorÚ __traceback__Úwith_traceback)ÚrequestÚexc_typeÚ exc_valueÚtbÚ status_code©rúm/var/www/tester-filtro-web/env/lib/python3.6/site-packages/django_extensions/management/technical_response.pyÚnull_technical_500_response s   r)r)Ú threadingZdjango.core.handlers.wsgirÚlocalr r rrrrrÚs