o hI @sddlmZddlZddlZddlZddlmZddlm Z ej r'ddl m Z edd d Z dddZee ZeeddddZdS)) annotationsN) LocalProxy)request)Appreturnt.TextIOcCstrtjdStjS)aFind the most appropriate error stream for the application. If a request is active, log to ``wsgi.errors``, otherwise use ``sys.stderr``. If you configure your own :class:`logging.StreamHandler`, you may want to use this for the stream. If you are using file or dict configuration and can't import this directly, you can refer to it as ``ext://flask.logging.wsgi_errors_stream``. z wsgi.errors)renvironsysstderrr r E/var/www/vip_panel/venv/lib/python3.10/site-packages/flask/logging.pywsgi_errors_streams rloggerlogging.LoggerboolcsF||}|r!tfdd|jDrdS|js dS|j}|sdS)zCheck if there is a handler in the logging chain that will handle the given logger's :meth:`effective level <~logging.Logger.getEffectiveLevel>`. c3s|]}|jkVqdS)Nlevel).0handlerrr r 'sz$has_level_handler..TF)getEffectiveLevelanyhandlers propagateparent)rcurrentr rr has_level_handlers rz6[%(asctime)s] %(levelname)s in %(module)s: %(message)sapprcCs:t|j}|jr|js|tjt|s|t |S)aGet the Flask app's logger and configure it if needed. The logger name will be the same as :attr:`app.import_name `. When :attr:`~flask.Flask.debug` is enabled, set the logger level to :data:`logging.DEBUG` if it is not set. If there is no handler for the logger's effective level, add a :class:`~logging.StreamHandler` for :func:`~flask.logging.wsgi_errors_stream` with a basic format. ) logging getLoggernamedebugrsetLevelDEBUGr addHandlerdefault_handler)rrr r r create_logger:s   r')rr)rrrr)rrrr) __future__rrr typingtwerkzeug.localrglobalsr TYPE_CHECKING sansio.apprrr StreamHandlerr& setFormatter Formatterr'r r r r s