ó ¸9—^c@sMddlZddlZddlmZejƒZde_dd„ZdS(iÿÿÿÿN(t WSGIHandleriôcCsqyFt|jjjjdƒtƒr0|t_ntjrEtj}nWntk rYnXt j |||ƒdS(s¿ 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. tselfN( t isinstancettb_nextttb_frametf_localstgetRttldtwsgi_tbtAttributeErrortsixtreraise(trequesttexc_typet exc_valuettbt status_code((sQ/tmp/pip-unpacked-wheel-a0M10Y/django_extensions/management/technical_response.pytnull_technical_500_response s!   ( t threadingR tdjango.core.handlers.wsgiRtlocalRtNoneRR(((sQ/tmp/pip-unpacked-wheel-a0M10Y/django_extensions/management/technical_response.pyts