_ @sdZddlZddlZddlZddlmZddlmZddlm Z ddl m Z ddl m Z ddl mZdd lmZdd lmZdd lmZdd lmZdd lmZddlmZddlmZddlmZddlmZddlmZddlmZddlmZddlmZddlm Z ddl!m"Z"ddl!m#Z#ddl!m$Z$ddl!m%Z%ddl&m'Z'ddl&m(Z(ddl)m*Z*ddl)m+Z+dd l)m,Z,dd!l-m.Z.dd"l-m/Z/dd#l-m0Z0dd$l-m1Z1dd%l2m3Z3dd&l2m4Z4dd'l2m5Z5dd(l2m6Z6dd)l2m7Z7dd*l2m8Z8dd+l2m9Z9dd,l2m:Z:dd-l2m;Z;dd.l m<Z<dd/l=m>Z>dd0l?m@Z@dd1lAmBZBdd2lAmCZCdd3lAmDZDdd4lAmEZEdd5lAmFZFdd6lGmHZHdd7lGmIZIdd8lGmJZJdd9lKmLZLdd:lKmMZMeNZOd;d<ZPd=d>ZQGd?d@d@e4ZRdS)Az flask.app ~~~~~~~~~ This module implements the central WSGI application object. :copyright: 2010 Pallets :license: BSD-3-Clause N) timedelta)update_wrapper)chain)Lock)Headers) ImmutableDict) BadRequest)BadRequestKeyError)default_exceptions) HTTPException)InternalServerError)MethodNotAllowed) BuildError)Map)RequestRedirect)RoutingException)Rule) BaseResponse)cli)json) integer_types)reraise) string_types) text_type)Config)ConfigAttribute)_AppCtxGlobals) AppContext)RequestContext)_request_ctx_stack)g)request)session)_endpoint_from_view_func)_PackageBoundObject) find_package)get_debug_flag)get_env)get_flashed_messages)get_load_dotenv)locked_cached_property)url_for)jsonify) create_logger)SecureCookieSessionInterface)appcontext_tearing_down)got_request_exception)request_finished)request_started)request_tearing_down)_default_template_ctx_processor)DispatchingJinjaLoader) Environment)Request)ResponsecCs t|tstd|S|S)Nseconds) isinstancer)valuer=*/tmp/pip-build-5gj8f0j9/flask/flask/app.py_make_timedeltaLs r?csfdd}t|S)zkWraps a method so that it performs a check in debug mode if the first request was already handled. cs.|jr|jrtd|||S)NamA setup function was called after the first request was handled. This usually indicates a bug in the application where a module was not imported and decorators or other functionality was called too late. To fix this make sure to import all your view modules, database models and everything related at a central place before the application starts serving requests.)debug_got_first_requestAssertionError)selfargskwargs)fr=r> wrapper_funcWs z!setupmethod..wrapper_func)r)rFrGr=)rFr> setupmethodRs rHc;@saeZdZdZeZeZeZ e Z e Z edZedZedZeddeZeddeZedZejZejZd d d giZed d dd dddd dd dd dedddddd dddddd dd dddddd dddd ded d!d"d d#dd$dd%d&d'dd(dd)dd*d+d,d d-d.iZeZ e!Z"d Z#d Z$e%Z&d Z'd Z(d Z)d d/d ddd0d dd d1d2 Z*e+d3d4Z,e-d5d6Z.e-d7d8Z/e+d9d:Z0e+d;d<Z1e-d=d>Z2dd?d@Z3dAdBZ4dCdDdEZ5e-dFdGZ6e6j7dHdGZ6dIdJZ8dKdLZ9dMdNZ:dOdPZ;dQdRZ<ed Z=e-dSdTZ>e>j7dUdTZ>d d d ddVdWZ?ddXdYZ@dZd[ZAd\d]ZBd^d_ZCd`daZDeEdbdcZFdddeZGeEd d d dfdgZHdhdiZIeEdjdkZJeKdldmZLeEdndoZMeEdpdqZNeEdrdsZOeEd dtduZPeEd dvdwZQeEd dxdyZReEd dzd{ZSeEd d|d}ZTeEd d~dZUeEddZVeEddZWeEddZXeEddZYeEddZZeEddZ[eEddZ\eEddZ]eEddZ^ddZ_ddZ`ddZaddZbddZcddZdddZeddZfddZgdddZhddZiddZjddZkddZlddZmddZnddZoddZpddZqerddZserddZtddZuddZvddZwddZxddZyddZzd S)FlaskagThe flask object implements a WSGI application and acts as the central object. It is passed the name of the module or package of the application. Once it is created it will act as a central registry for the view functions, the URL rules, template configuration and much more. The name of the package is used to resolve resources from inside the package or the folder the module is contained in depending on if the package parameter resolves to an actual python package (a folder with an :file:`__init__.py` file inside) or a standard module (just a ``.py`` file). For more information about resource loading, see :func:`open_resource`. Usually you create a :class:`Flask` instance in your main module or in the :file:`__init__.py` file of your package like this:: from flask import Flask app = Flask(__name__) .. admonition:: About the First Parameter The idea of the first parameter is to give Flask an idea of what belongs to your application. This name is used to find resources on the filesystem, can be used by extensions to improve debugging information and a lot more. So it's important what you provide there. If you are using a single module, `__name__` is always the correct value. If you however are using a package, it's usually recommended to hardcode the name of your package there. For example if your application is defined in :file:`yourapplication/app.py` you should create it with one of the two versions below:: app = Flask('yourapplication') app = Flask(__name__.split('.')[0]) Why is that? The application will work even with `__name__`, thanks to how resources are looked up. However it will make debugging more painful. Certain extensions can make assumptions based on the import name of your application. For example the Flask-SQLAlchemy extension will look for the code in your application that triggered an SQL query in debug mode. If the import name is not properly set up, that debugging information is lost. (For example it would only pick up SQL queries in `yourapplication.app` and not `yourapplication.views.frontend`) .. versionadded:: 0.7 The `static_url_path`, `static_folder`, and `template_folder` parameters were added. .. versionadded:: 0.8 The `instance_path` and `instance_relative_config` parameters were added. .. versionadded:: 0.11 The `root_path` parameter was added. .. versionadded:: 1.0 The ``host_matching`` and ``static_host`` parameters were added. .. versionadded:: 1.0 The ``subdomain_matching`` parameter was added. Subdomain matching needs to be enabled manually now. Setting :data:`SERVER_NAME` does not implicitly enable it. :param import_name: the name of the application package :param static_url_path: can be used to specify a different path for the static files on the web. Defaults to the name of the `static_folder` folder. :param static_folder: The folder with static files that is served at ``static_url_path``. Relative to the application ``root_path`` or an absolute path. Defaults to ``'static'``. :param static_host: the host to use when adding the static route. Defaults to None. Required when using ``host_matching=True`` with a ``static_folder`` configured. :param host_matching: set ``url_map.host_matching`` attribute. Defaults to False. :param subdomain_matching: consider the subdomain relative to :data:`SERVER_NAME` when matching routes. Defaults to False. :param template_folder: the folder that contains the templates that should be used by the application. Defaults to ``'templates'`` folder in the root path of the application. :param instance_path: An alternative instance path for the application. By default the folder ``'instance'`` next to the package or module is assumed to be the instance path. :param instance_relative_config: if set to ``True`` relative filenames for loading the config are assumed to be relative to the instance path instead of the application root. :param root_path: Flask by default will automatically calculate the path to the root of the application. In certain situations this cannot be achieved (for instance if the package is a Python 3 namespace package) and needs to be manually defined. ZTESTINGZ SECRET_KEYZSESSION_COOKIE_NAMEZPERMANENT_SESSION_LIFETIMEZ get_converterZSEND_FILE_MAX_AGE_DEFAULTZUSE_X_SENDFILE extensionszjinja2.ext.autoescapezjinja2.ext.with_ENVNDEBUGFPROPAGATE_EXCEPTIONSPRESERVE_CONTEXT_ON_EXCEPTIONdays SERVER_NAMEAPPLICATION_ROOT/r#ZSESSION_COOKIE_DOMAINZSESSION_COOKIE_PATHZSESSION_COOKIE_HTTPONLYTZSESSION_COOKIE_SECUREZSESSION_COOKIE_SAMESITEZSESSION_REFRESH_EACH_REQUESTZMAX_CONTENT_LENGTHhours TRAP_BAD_REQUEST_ERRORSTRAP_HTTP_EXCEPTIONSZEXPLAIN_TEMPLATE_LOADINGPREFERRED_URL_SCHEMEhttpZ JSON_AS_ASCIIZJSON_SORT_KEYSZJSONIFY_PRETTYPRINT_REGULARZJSONIFY_MIMETYPEzapplication/jsonTEMPLATES_AUTO_RELOADZMAX_COOKIE_SIZEistaticZ templatesc Cstj||d|d| ||_||_|dkrI|j}ntjj|sgtd||_ |j | |_ i|_ i|_ g|_i|_g|_i|_i|_g|_i|_i|_dtgi|_g|_i|_g|_i|_|j|_||j_||_d|_ t!|_"|j#rt$||ksrt%d|j&|jdddd |d |j'|j(|j)_(dS) Ntemplate_folder root_pathzWIf an instance path is provided it must be absolute. A relative path was given instead.Fz-Invalid static_host/host_matching combinationz/endpointr[host view_func)*r%__init__static_url_path static_folderauto_find_instance_pathospathisabs ValueError instance_path make_configconfigview_functionserror_handler_specurl_build_error_handlersbefore_request_funcsbefore_first_request_funcsafter_request_funcsteardown_request_funcsteardown_appcontext_funcsurl_value_preprocessorsurl_default_functionsr5template_context_processorsshell_context_processors blueprints_blueprint_orderrJ url_map_classurl_map host_matchingsubdomain_matchingrAr_before_request_lockZhas_static_folderboolrB add_url_ruleZsend_static_filenamer) rC import_namerbrcZ static_hostr|r}r\riZinstance_relative_configr]r=r=r>rasP                       zFlask.__init__cCs_|jdkrXttjddd}|dkr8dStjjtjj|dS|jS)a_The name of the application. This is usually the import name with the difference that it's guessed from the run file if the import name is main. This name is used as a display name when Flask needs the name of the application. It can be set and overridden to change the value. .. versionadded:: 0.8 __main____file__Nr)rgetattrsysmodulesrerfsplitextbasename)rCfnr=r=r>rds   z Flask.namecCs-|jd}|dk r|S|jp,|jS)zReturns the value of the ``PROPAGATE_EXCEPTIONS`` configuration value in case it's set, otherwise a sensible default is returned. .. versionadded:: 0.7 rMN)rktestingr@)rCrvr=r=r>propagate_exceptionsus  zFlask.propagate_exceptionscCs$|jd}|dk r|S|jS)zReturns the value of the ``PRESERVE_CONTEXT_ON_EXCEPTION`` configuration value in case it's set, otherwise a sensible default is returned. .. versionadded:: 0.7 rNN)rkr@)rCrr=r=r>preserve_context_on_exceptions  z#Flask.preserve_context_on_exceptioncCs t|S)aA standard Python :class:`~logging.Logger` for the app, with the same name as :attr:`name`. In debug mode, the logger's :attr:`~logging.Logger.level` will be set to :data:`~logging.DEBUG`. If there are no handlers configured, a default handler will be added. See :doc:`/logging` for more information. .. versionchanged:: 1.1.0 The logger takes the same name as :attr:`name` rather than hard-coding ``"flask.app"``. .. versionchanged:: 1.0.0 Behavior was simplified. The logger is always named ``"flask.app"``. The level is only set during configuration, it doesn't check ``app.debug`` each time. Only one format is used, not different ones depending on ``app.debug``. No handlers are removed, and a handler is only added if no handlers are already configured. .. versionadded:: 0.3 )r.)rCr=r=r>loggersz Flask.loggercCs |jS)zThe Jinja environment used to load templates. The environment is created the first time this property is accessed. Changing :attr:`jinja_options` after that will have no effect. )create_jinja_environment)rCr=r=r> jinja_envszFlask.jinja_envcCs|jS)zThis attribute is set to ``True`` if the application started handling the first request. .. versionadded:: 0.8 )rA)rCr=r=r>got_first_requestszFlask.got_first_requestcCsQ|j}|r|j}t|j}t|drjs    zFlask.make_configcCsQt|j\}}|dkr4tjj|dStjj|d|jdS)aTries to locate the instance path if it was not provided to the constructor of the application class. It will basically calculate the path to a folder named ``instance`` next to your main file or the package. .. versionadded:: 0.8 Ninstancevarz -instance)r&rrerfjoinr)rCprefixZ package_pathr=r=r>rds zFlask.auto_find_instance_pathrbcCsttjj|j||S)aOpens a resource from the application's instance folder (:attr:`instance_path`). Otherwise works like :meth:`open_resource`. Instance resources can also be opened for writing. :param resource: the name of the resource. To access resources within subfolders use forward slashes as separator. :param mode: resource file opening mode, default is 'rb'. )openrerfrri)rCresourcemoder=r=r>open_instance_resources zFlask.open_instance_resourcecCs$|jd}|dk r|S|jS)amReload templates when they are changed. Used by :meth:`create_jinja_environment`. This attribute can be configured with :data:`TEMPLATES_AUTO_RELOAD`. If not set, it will be enabled in debug mode. .. versionadded:: 1.0 This property was added but the underlying config and behavior already existed. rZN)rkr@)rCrr=r=r>templates_auto_reloads zFlask.templates_auto_reloadcCs||jdrsc Cst|j}d|kr(|j|drs       zFlask.create_jinja_environmentcCs t|S)aCreates the loader for the Jinja2 environment. Can be used to override just the loader and keeping the rest unchanged. It's discouraged to override this function. Instead one should override the :meth:`jinja_loader` function instead. The global loader dispatches between the loaders of the application and the individual blueprints. .. versionadded:: 0.7 )r6)rCr=r=r>create_global_jinja_loaders z Flask.create_global_jinja_loadercCs|dkrdS|jdS)zReturns ``True`` if autoescaping should be active for the given template name. If no template name is given, returns `True`. .. versionadded:: 0.5 NT.html.htm.xml.xhtml)rrrr)endswith)rCfilenamer=r=r>r)s zFlask.select_jinja_autoescapecCs|jd}tj}|dk r_|jj}|dk r_||jkr_t||j|}|j}x|D]}|j|qrW|j|dS)aUpdate the template context with some commonly used variables. This injects request, session, config and g into the template context as well as everything template context processors want to inject. Note that the as of Flask 0.6, the original values in the context will not be overridden if a context processor decides to return a value with the same key. :param context: the context as a dictionary that is updated in place to add extra variables. N)rvr topr" blueprintrcopyr)rCcontextfuncsZreqctxbpZorig_ctxfuncr=r=r>update_template_context3s      zFlask.update_template_contextcCs:d|dti}x!|jD]}|j|qW|S)zReturns the shell context for an interactive shell for this application. This runs all the registered shell context processors. .. versionadded:: 0.11 Zappr!)r!rwr)rCr processorr=r=r>make_shell_contextLszFlask.make_shell_contextcCs |jdS)avWhether debug mode is enabled. When using ``flask run`` to start the development server, an interactive debugger will be shown for unhandled exceptions, and the server will be reloaded when code changes. This maps to the :data:`DEBUG` config key. This is enabled when :attr:`env` is ``'development'`` and is overridden by the ``FLASK_DEBUG`` environment variable. It may not behave as expected if set in code. **Do not enable debug mode when deploying in production.** Default: ``True`` if :attr:`env` is ``'development'``, or ``False`` otherwise. rL)rk)rCr=r=r>r@csz Flask.debugcCs ||jd<|j|j_dS)NrL)rkrrr)rCr<r=r=r>r@ts c Kstjjddkr3ddlm}|dSt|rtjdtjkrst|_ t |_ ndtjkrt |_ |dk rt ||_ d}d }|j jd } d\} } | r| jd \} } } |p| p|}ttd d || fD|}|jd|j |jd|j |jddtj|j |j |jdddlm} z| ||||Wdd|_XdS)a Runs the application on a local development server. Do not use ``run()`` in a production setting. It is not intended to meet security and performance requirements for a production server. Instead, see :ref:`deployment` for WSGI server recommendations. If the :attr:`debug` flag is set the server will automatically reload for code changes and show a debugger in case an exception happened. If you want to run the application in debug mode, but disable the code execution on the interactive debugger, you can pass ``use_evalex=False`` as parameter. This will keep the debugger's traceback screen active, but disable code execution. It is not recommended to use this function for development with automatic reloading as this is badly supported. Instead you should be using the :command:`flask` command line script's ``run`` support. .. admonition:: Keep in Mind Flask will suppress any server error with a generic error page unless it is in debug mode. As such to enable just the interactive debugger without the code reloading, you have to invoke :meth:`run` with ``debug=True`` and ``use_reloader=False``. Setting ``use_debugger`` to ``True`` without being in debug mode won't catch any exceptions because there won't be any to catch. :param host: the hostname to listen on. Set this to ``'0.0.0.0'`` to have the server available externally as well. Defaults to ``'127.0.0.1'`` or the host in the ``SERVER_NAME`` config variable if present. :param port: the port of the webserver. Defaults to ``5000`` or the port defined in the ``SERVER_NAME`` config variable if present. :param debug: if given, enable or disable debug mode. See :attr:`debug`. :param load_dotenv: Load the nearest :file:`.env` and :file:`.flaskenv` files to set environment variables. Will also change the working directory to the directory containing the first file found. :param options: the options to be forwarded to the underlying Werkzeug server. See :func:`werkzeug.serving.run_simple` for more information. .. versionchanged:: 1.0 If installed, python-dotenv will be used to load environment variables from :file:`.env` and :file:`.flaskenv` files. If set, the :envvar:`FLASK_ENV` and :envvar:`FLASK_DEBUG` environment variables will override :attr:`env` and :attr:`debug`. Threaded mode is enabled by default. .. versionchanged:: 0.10 The default port is now picked from the ``SERVER_NAME`` variable. ZFLASK_RUN_FROM_CLItruer)explain_ignored_app_runNZ FLASK_ENVZ FLASK_DEBUGz 127.0.0.1irQ:css!|]}|dk r|VqdS)Nr=).0pr=r=r> szFlask.run..Z use_reloaderZ use_debuggerthreadedTFr) run_simple)NN)reenvironget debughelpersrr*r load_dotenvr(envr'r@rrk partitionintnext setdefaultZshow_server_bannerrZwerkzeug.servingrrA)rCr_portr@rrr_hostZ_port server_nameZsn_hostZsn_port_rr=r=r>runys:<      (z Flask.runcKs>|j}|dkr%ddlm}|||jd||S)aCreates a test client for this application. For information about unit testing head over to :ref:`testing`. Note that if you are testing for assertions or exceptions in your application code, you must set ``app.testing = True`` in order for the exceptions to propagate to the test client. Otherwise, the exception will be handled by the application (not visible to the test client) and the only indication of an AssertionError or other exception will be a 500 status code response to the test client. See the :attr:`testing` attribute. For example:: app.testing = True client = app.test_client() The test client can be used in a ``with`` block to defer the closing down of the context until the end of the ``with`` block. This is useful if you want to access the context locals for testing:: with app.test_client() as c: rv = c.get('/?vodka=42') assert request.args['vodka'] == '42' Additionally, you may pass optional keyword arguments that will then be passed to the application's :attr:`test_client_class` constructor. For example:: from flask.testing import FlaskClient class CustomClient(FlaskClient): def __init__(self, *args, **kwargs): self._authentication = kwargs.pop("authentication") super(CustomClient,self).__init__( *args, **kwargs) app.test_client_class = CustomClient client = app.test_client(authentication='Basic ....') See :class:`~flask.testing.FlaskClient` for more information. .. versionchanged:: 0.4 added support for ``with`` block usage for the client. .. versionadded:: 0.7 The `use_cookies` parameter was added as well as the ability to override the client to be used by setting the :attr:`test_client_class` attribute. .. versionchanged:: 0.11 Added `**kwargs` to support passing additional keyword arguments to the constructor of :attr:`test_client_class`. Nr) FlaskClient use_cookies)test_client_classrrresponse_class)rCrrEclsr=r=r> test_clients3  zFlask.test_clientcKs2|j}|dkr%ddlm}|||S)a-Create a CLI runner for testing CLI commands. See :ref:`testing-cli`. Returns an instance of :attr:`test_cli_runner_class`, by default :class:`~flask.testing.FlaskCliRunner`. The Flask app object is passed as the first argument. .. versionadded:: 1.0 Nr)FlaskCliRunner)test_cli_runner_classrr)rCrErr=r=r>test_cli_runners  zFlask.test_cli_runnercCs&tjtd|jj||S)aCreates or opens a new session. Default implementation stores all session data in a signed cookie. This requires that the :attr:`secret_key` is set. Instead of overriding this method we recommend replacing the :class:`session_interface`. .. deprecated: 1.0 Will be removed in 2.0. Use ``session_interface.open_session`` instead. :param request: an instance of :attr:`request_class`. zf"open_session" is deprecated and will be removed in 2.0. Use "session_interface.open_session" instead.)warningswarnDeprecationWarningsession_interface open_session)rCr"r=r=r>r.s  zFlask.open_sessioncCs)tjtd|jj|||S)a2Saves the session if it needs updates. For the default implementation, check :meth:`open_session`. Instead of overriding this method we recommend replacing the :class:`session_interface`. .. deprecated: 1.0 Will be removed in 2.0. Use ``session_interface.save_session`` instead. :param session: the session to be saved (a :class:`~werkzeug.contrib.securecookie.SecureCookie` object) :param response: an instance of :attr:`response_class` zf"save_session" is deprecated and will be removed in 2.0. Use "session_interface.save_session" instead.)rrrr save_session)rCr#responser=r=r>rCs zFlask.save_sessioncCs#tjtd|jj|S)a7Creates a new instance of a missing session. Instead of overriding this method we recommend replacing the :class:`session_interface`. .. deprecated: 1.0 Will be removed in 2.0. Use ``session_interface.make_null_session`` instead. .. versionadded:: 0.7 zp"make_null_session" is deprecated and will be removed in 2.0. Use "session_interface.make_null_session" instead.)rrrrmake_null_session)rCr=r=r>rZs  zFlask.make_null_sessioncKsd}|j|jkrW|j|j|ks}td||j|j|jfn&||j|j<|jj|d}|j|||dS)aaRegister a :class:`~flask.Blueprint` on the application. Keyword arguments passed to this method will override the defaults set on the blueprint. Calls the blueprint's :meth:`~flask.Blueprint.register` method after recording the blueprint in the application's :attr:`blueprints`. :param blueprint: The blueprint to register. :param url_prefix: Blueprint routes will be prefixed with this. :param subdomain: Blueprint routes will match on this subdomain. :param url_defaults: Blueprint routes will use these default values for view arguments. :param options: Additional keyword arguments are passed to :class:`~flask.blueprints.BlueprintSetupState`. They can be accessed in :meth:`~flask.Blueprint.record` callbacks. .. versionadded:: 0.7 FzA name collision occurred between blueprints %r and %r. Both share the same name "%s". Blueprints that are created on the fly need unique names.TN)rrxrBryappendregister)rCrrZfirst_registrationr=r=r>register_blueprintns#zFlask.register_blueprintcCs t|jS)zhIterates over all blueprints by the order they were registered. .. versionadded:: 0.11 )iterry)rCr=r=r>iter_blueprintsszFlask.iter_blueprintsc Ks|dkrt|}||d<|jdd}|dkrXt|ddpUd}t|trstdtdd|D}tt|df}|dkrt|d d}|dkrd |krd }|jd nd }||O}|j|d||}||_ |j j||dk r|j j |}|dk rw||krwt d |||j |rsz%Flask.add_url_rule..required_methodsprovide_automatic_optionsOPTIONSTFzFView function mapping is overwriting an existing endpoint function: %s)r)r$poprr;r TypeErrorsetaddurl_rule_classrr{rlrrB) rCruler^r`rrrrZold_funcr=r=r>rs<=            zFlask.add_url_rulec sfdd}|S)aA decorator that is used to register a view function for a given URL rule. This does the same thing as :meth:`add_url_rule` but is intended for decorator usage:: @app.route('/') def index(): return 'Hello World' For more information refer to :ref:`url-route-registrations`. :param rule: the URL rule as string :param endpoint: the endpoint for the registered URL rule. Flask itself assumes the name of the view function as endpoint :param options: the options to be forwarded to the underlying :class:`~werkzeug.routing.Rule` object. A change to Werkzeug is handling of method options. methods is a list of methods this rule should be limited to (``GET``, ``POST`` etc.). By default a rule just listens for ``GET`` (and implicitly ``HEAD``). Starting with Flask 0.6, ``OPTIONS`` is implicitly added and handled by the standard request handling. cs,jdd}j|||S)Nr^)rr)rFr^)rrrCr=r> decorator!szFlask.route..decoratorr=)rCrrrr=)rrrCr>routesz Flask.routecsfdd}|S)zA decorator to register a function as an endpoint. Example:: @app.endpoint('example.endpoint') def example(): return "example" :param endpoint: the name of the endpoint cs|j<|S)N)rl)rF)r^rCr=r>r4s z!Flask.endpoint..decoratorr=)rCr^rr=)r^rCr>r^(s zFlask.endpointcCsat|trt|}n|}t|ts7tt|trS||jfS|dfSdS)a Get the exception class being handled. For HTTP status codes or ``HTTPException`` subclasses, return both the exception and status code. :param exc_class_or_code: Any exception class, or an HTTP status code as an integer. N)r;rr issubclass ExceptionrBr code)Zexc_class_or_code exc_classr=r=r>_get_exc_class_and_code:s   zFlask._get_exc_class_and_codecsfdd}|S)a7Register a function to handle errors by code or exception class. A decorator that is used to register a function given an error code. Example:: @app.errorhandler(404) def page_not_found(error): return 'This page does not exist', 404 You can also register handlers for arbitrary exceptions:: @app.errorhandler(DatabaseError) def special_exception_handler(error): return 'Database connection failed', 500 .. versionadded:: 0.7 Use :meth:`register_error_handler` instead of modifying :attr:`error_handler_spec` directly, for application wide error handlers. .. versionadded:: 0.7 One can now additionally also register custom exception types that do not necessarily have to be a subclass of the :class:`~werkzeug.exceptions.HTTPException` class. :param code_or_exception: the code as integer for the handler, or an arbitrary exception csjd||S)N)_register_error_handler)rF)code_or_exceptionrCr=r>rnsz%Flask.errorhandler..decoratorr=)rCrrr=)rrCr> errorhandlerOszFlask.errorhandlercCs|jd||dS)zAlternative error attach function to the :meth:`errorhandler` decorator that is more straightforward to use for non decorator usage. .. versionadded:: 0.7 N)r)rCrrFr=r=r>register_error_handlertszFlask.register_error_handlerc Cst|tr$tdj|y|j|\}}Wn'tk rftdj|YnX|jj|ij|i}|||r~s  !zFlask._register_error_handlercsfdd}|S)aA decorator that is used to register custom template filter. You can specify a name for the filter, otherwise the function name will be used. Example:: @app.template_filter() def reverse(s): return s[::-1] :param name: the optional name of the filter, otherwise the function name will be used. csj|d|S)Nr)add_template_filter)rF)rrCr=r>rsz(Flask.template_filter..decoratorr=)rCrrr=)rrCr>template_filterszFlask.template_filtercCs||jj|p|jrszFlask.add_template_filtercsfdd}|S)aSA decorator that is used to register custom template test. You can specify a name for the test, otherwise the function name will be used. Example:: @app.template_test() def is_prime(n): if n == 2: return True for i in range(2, int(math.ceil(math.sqrt(n))) + 1): if n % i == 0: return False return True .. versionadded:: 0.10 :param name: the optional name of the test, otherwise the function name will be used. csj|d|S)Nr)add_template_test)rF)rrCr=r>rsz&Flask.template_test..decoratorr=)rCrrr=)rrCr> template_testszFlask.template_testcCs||jj|p|jrs zFlask.add_template_testcsfdd}|S)aA decorator that is used to register a custom template global function. You can specify a name for the global function, otherwise the function name will be used. Example:: @app.template_global() def double(n): return 2 * n .. versionadded:: 0.10 :param name: the optional name of the global function, otherwise the function name will be used. csj|d|S)Nr)add_template_global)rF)rrCr=r>rsz(Flask.template_global..decoratorr=)rCrrr=)rrCr>template_globalszFlask.template_globalcCs||jj|p|jrs zFlask.add_template_globalcCs |jjdgj||S)aRegisters a function to run before each request. For example, this can be used to open a database connection, or to load the logged in user from the session. The function will be called without any arguments. If it returns a non-None value, the value is handled as if it was the return value from the view, and further request handling is stopped. N)rorr)rCrFr=r=r>before_requests zFlask.before_requestcCs|jj||S)zRegisters a function to be run before the first request to this instance of the application. The function will be called without any arguments and its return value is ignored. .. versionadded:: 0.8 )rpr)rCrFr=r=r>before_first_request s zFlask.before_first_requestcCs |jjdgj||S)auRegister a function to be run after each request. Your function must take one parameter, an instance of :attr:`response_class` and return a new response object or the same (see :meth:`process_response`). As of Flask 0.7 this function might not be executed at the end of the request in case an unhandled exception occurred. N)rqrr)rCrFr=r=r> after_requests zFlask.after_requestcCs |jjdgj||S)aRegister a function to be run at the end of each request, regardless of whether there was an exception or not. These functions are executed when the request context is popped, even if not an actual request was performed. Example:: ctx = app.test_request_context() ctx.push() ... ctx.pop() When ``ctx.pop()`` is executed in the above example, the teardown functions are called just before the request context moves from the stack of active contexts. This becomes relevant if you are using such constructs in tests. Generally teardown functions must take every necessary step to avoid that they will fail. If they do execute code that might fail they will have to surround the execution of these code by try/except statements and log occurring errors. When a teardown function was called because of an exception it will be passed an error object. The return values of teardown functions are ignored. .. admonition:: Debug Note In debug mode Flask will not tear down a request on an exception immediately. Instead it will keep it alive so that the interactive debugger can still access it. This behavior can be controlled by the ``PRESERVE_CONTEXT_ON_EXCEPTION`` configuration variable. N)rrrr)rCrFr=r=r>teardown_request's$zFlask.teardown_requestcCs|jj||S)aRegisters a function to be called when the application context ends. These functions are typically also called when the request context is popped. Example:: ctx = app.app_context() ctx.push() ... ctx.pop() When ``ctx.pop()`` is executed in the above example, the teardown functions are called just before the app context moves from the stack of active contexts. This becomes relevant if you are using such constructs in tests. Since a request context typically also manages an application context it would also be called when you pop a request context. When a teardown function was called because of an unhandled exception it will be passed an error object. If an :meth:`errorhandler` is registered, it will handle the exception and the teardown will not receive it. The return values of teardown functions are ignored. .. versionadded:: 0.9 )rsr)rCrFr=r=r>teardown_appcontextNszFlask.teardown_appcontextcCs|jdj||S)z0Registers a template context processor function.N)rvr)rCrFr=r=r>context_processoroszFlask.context_processorcCs|jj||S)zVRegisters a shell context processor function. .. versionadded:: 0.11 )rwr)rCrFr=r=r>shell_context_processoruszFlask.shell_context_processorcCs |jjdgj||S)a#Register a URL value preprocessor function for all view functions in the application. These functions will be called before the :meth:`before_request` functions. The function can modify the values captured from the matched url before they are passed to the view. For example, this can be used to pop a common language code value and place it in ``g`` rather than pass it to every view. The function is passed the endpoint name and values dict. The return value is ignored. N)rtrr)rCrFr=r=r>url_value_preprocessor~szFlask.url_value_preprocessorcCs |jjdgj||S)zCallback function for URL defaults for all view functions of the application. It's called with the endpoint and values and should update the values passed in place. N)rurr)rCrFr=r=r> url_defaultsszFlask.url_defaultsc Cs|jt|\}}xtj|fd|ftjdfdfD]f\}}|jj|ij|}|syqFx0|jD]%}|j|}|dk r|SqWqFWdS)a(Return a registered error handler for an exception in this order: blueprint handler for a specific code, app handler for a specific code, blueprint handler for an exception class, app handler for an exception class, or ``None`` if a suitable handler is not found. N)NN)rtyper"rrmrr__mro__) rCerrrcZ handler_maprhandlerr=r=r>_find_error_handlers    zFlask._find_error_handlercCsO|jdkr|St|tr&|S|j|}|dkrE|S||S)acHandles an HTTP exception. By default this will invoke the registered error handlers and fall back to returning the exception as response. .. versionchanged:: 1.0.3 ``RoutingException``, used internally for actions such as slash redirects during routing, is not passed to error handlers. .. versionchanged:: 1.0 Exceptions are looked up by code *and* by MRO, so ``HTTPExcpetion`` subclasses can be handled with a catch-all handler for the base ``HTTPException``. .. versionadded:: 0.3 N)rr;rr)rCrrr=r=r>handle_http_exceptions zFlask.handle_http_exceptioncCs]|jdrdS|jd}|dkrF|jrFt|trFdS|rYt|tSdS)aChecks if an HTTP exception should be trapped or not. By default this will return ``False`` for all exceptions except for a bad request key error if ``TRAP_BAD_REQUEST_ERRORS`` is set to ``True``. It also returns ``True`` if ``TRAP_HTTP_EXCEPTIONS`` is set to ``True``. This is called for all HTTP exceptions raised by a view function. If it returns ``True`` for any exception the error handler for this exception is not called and it shows up as regular exception in the traceback. This is helpful for debugging implicitly raised HTTP exceptions. .. versionchanged:: 1.0 Bad request errors are not trapped by default in debug mode. .. versionadded:: 0.8 rWTrVNF)rkr@r;r r)rCrZtrap_bad_requestr=r=r>trap_http_exceptions     zFlask.trap_http_exceptioncCstj\}}}||ks'tt|tr|jsL|jdrd|_|jd|j krdj |j|_ nt tdsf|_t|t r|j| r|j|S|j|}|dkrt|||||S)a>This method is called whenever an exception occurs that should be handled. A special case is :class:`~werkzeug .exceptions.HTTPException` which is forwarded to the :meth:`handle_http_exception` method. This function will either return a response value or reraise the exception with the same traceback. .. versionchanged:: 1.0 Key errors raised from request data like ``form`` show the bad key in debug mode rather than a generic bad request message. .. versionadded:: 0.7 rVTrzKeyError: '{}'show_exceptionN)rexc_inforBr;r r@rkrrDget_descriptionr descriptionhasattrr rrrr)rCrexc_type exc_valuetbrr=r=r>handle_user_exceptions    zFlask.handle_user_exceptioncCstj\}}}tj|d||jrV||krPt|||n||j|||ft}||_|j |}|dk r||}|j |ddS)aHandle an exception that did not have an error handler associated with it, or that was raised from an error handler. This always causes a 500 ``InternalServerError``. Always sends the :data:`got_request_exception` signal. If :attr:`propagate_exceptions` is ``True``, such as in debug mode, the error will be re-raised so that the debugger can display it. Otherwise, the original exception is logged, and an :exc:`~werkzeug.exceptions.InternalServerError` is returned. If an error handler is registered for ``InternalServerError`` or ``500``, it will be used. For consistency, the handler will always receive the ``InternalServerError``. The original unhandled exception is available as ``e.original_exception``. .. note:: Prior to Werkzeug 1.0.0, ``InternalServerError`` will not always have an ``original_exception`` attribute. Use ``getattr(e, "original_exception", None)`` to simulate the behavior for compatibility. .. versionchanged:: 1.1.0 Always passes the ``InternalServerError`` instance to the handler, setting ``original_exception`` to the unhandled error. .. versionchanged:: 1.1.0 ``after_request`` functions and other finalization is done even for the default 500 response when there is no handler. .. versionadded:: 0.3 exceptionNfrom_error_handlerT) rrr1sendrr log_exceptionr Zoriginal_exceptionrfinalize_request)rCrr r!r" server_errorrr=r=r>handle_exception s"      zFlask.handle_exceptioncCs*|jjdtjtjfd|dS)a Logs an exception. This is called by :meth:`handle_exception` if debugging is disabled and right before the handler is called. The default implementation logs the exception as error on the :attr:`logger`. .. versionadded:: 0.8 zException on %s [%s]rN)rerrorr"rfmethod)rCrr=r=r>r'[s zFlask.log_exceptioncCsU|j s,t|jt s,|jdkr5|jddlm}||dS)a.Exceptions that are recording during routing are reraised with this method. During debug we are not reraising redirect requests for non ``GET``, ``HEAD``, or ``OPTIONS`` requests and we're raising a different error instead to help debug situations. :internal: rHEADrr)FormDataRoutingRedirectN)rr-r)r@r;routing_exceptionrr,rr.)rCr"r.r=r=r>raise_routing_exceptiongs  zFlask.raise_routing_exceptioncCsstjj}|jdk r(|j||j}t|ddr\|jdkr\|jS|j |j |j S)aDoes the request dispatching. Matches the URL and returns the return value of the view or error handler. This does not have to be a response object. In order to convert the return value to a proper response object, call :func:`make_response`. .. versionchanged:: 0.7 This no longer does the exception handling, this code was moved to the new :meth:`full_dispatch_request`. NrFr) r rr"r/r0Zurl_rulerr,make_default_options_responserlr^ view_args)rCreqrr=r=r>dispatch_requestzs    zFlask.dispatch_requestcCs|jy5tj||j}|dkr>|j}Wn4tk ru}z|j|}WYdd}~XnX|j|S)zDispatches the request and on top of that performs request pre and postprocessing as well as HTTP exception catching and error handling. .. versionadded:: 0.7 N)*try_trigger_before_first_request_functionsr3r&preprocess_requestr4rr#r()rCrrr=r=r>full_dispatch_requests    "zFlask.full_dispatch_requestc Csg|j|}y&|j|}tj|d|Wn+tk rb|sN|jjdYnX|S)a)Given the return value from a view function this finalizes the request by converting it into a response and invoking the postprocessing functions. This is invoked for both normal request dispatching as well as error handlers. Because this means that it might be called as a result of a failure a special safe mode is available which can be enabled with the `from_error_handler` flag. If enabled, failures in response processing will be logged and otherwise ignored. :internal: rz?Request finalizing failed with an error while handling an error) make_responseprocess_responser2r&rrr$)rCrr%rr=r=r>r(s    zFlask.finalize_requestc CsS|jr dS|j6|jr$dSx|jD] }|q.Wd|_WdQRXdS)zCalled before each request and will ensure that it triggers the :attr:`before_first_request_funcs` and only exactly once per application instance (which means process usually). :internal: NT)rAr~rp)rCrr=r=r>r5s    z0Flask.try_trigger_before_first_request_functionscCstjj}t|dr*|j}n\g}y|jddWn?tk rt}z|j}WYdd}~Xntk rYnX|j }|j j ||S)zThis method is called to create the default ``OPTIONS`` response. This can be changed through subclassing to change the default behavior of ``OPTIONS`` responses. .. versionadded:: 0.7 allowed_methodsr,z--N) r rZ url_adapterrr:matchr Z valid_methodsr rZallowr)rCadapterrrrr=r=r>r1s   z#Flask.make_default_options_responsecCsdS)a This is called to figure out if an error should be ignored or not as far as the teardown system is concerned. If this function returns ``True`` then the teardown handlers will not be passed the error. .. versionadded:: 0.10 Fr=)rCr+r=r=r>should_ignore_errorszFlask.should_ignore_errorcCs%d}}t|trt|}|dkrC|\}}}nU|dkrt|dttttfr}|\}}q|\}}n td|dkrtdt||jst|tt t fr|j|d|d|}d}}nt|tr t |}nt|t s;t |ry|jj|tj}Wqtk r}z=td jd |d |}tt|tjdWYdd}~XqXntd jd ||dk r t|tt t fr||_n ||_|r!|jj||S) aConvert the return value from a view function to an instance of :attr:`response_class`. :param rv: the return value from the view function. The view function must return a response. Returning ``None``, or the view ending without returning, is not allowed. The following types are allowed for ``view_rv``: ``str`` (``unicode`` in Python 2) A response object is created with the string encoded to UTF-8 as the body. ``bytes`` (``str`` in Python 2) A response object is created with the bytes as the body. ``dict`` A dictionary that will be jsonify'd before being returned. ``tuple`` Either ``(body, status, headers)``, ``(body, status)``, or ``(body, headers)``, where ``body`` is any of the other types allowed here, ``status`` is a string or an integer, and ``headers`` is a dictionary or a list of ``(key, value)`` tuples. If ``body`` is a :attr:`response_class` instance, ``status`` overwrites the exiting value and ``headers`` are extended. :attr:`response_class` The object is returned unchanged. other :class:`~werkzeug.wrappers.Response` class The object is coerced to :attr:`response_class`. :func:`callable` The function is called as a WSGI application. The result is used to create a response object. .. versionchanged:: 0.9 Previously a tuple was interpreted as the arguments for the response object. NrzThe view function did not return a valid response tuple. The tuple must have the form (body, status, headers), (body, status), or (body, headers).zyThe view function did not return a valid response. The function either returned None or ended without a return statement.statusheadersz{e} The view function did not return a valid response. The return type must be a string, dict, tuple, Response instance, or WSGI callable, but it was a {rv.__class__.__name__}.rrzThe view function did not return a valid response. The return type must be a string, dict, tuple, Response instance, or WSGI callable, but it was a {rv.__class__.__name__}.)r;tuplelenrrlistrrrbytes bytearrayr-rcallableZ force_typer"rrrrrr@ status_coderAextend)rCrr@rAZlen_rvrZ new_errorr=r=r>r8sL+         0     zFlask.make_responsecCs|dk rS|js'|jjp*dnd}|jj|jd|jdd|S|jddk r|jj|jdd|jdd|jdSdS) a*Creates a URL adapter for the given request. The URL adapter is created at a point where the request context is not yet set up so the request is passed explicitly. .. versionadded:: 0.6 .. versionchanged:: 0.9 This can now also be called without a request object when the URL adapter is created for the application context. .. versionchanged:: 1.0 :data:`SERVER_NAME` no longer implicitly enables subdomain matching. Use :attr:`subdomain_matching` instead. NrrQ subdomain script_namerRZ url_schemerX)r}r{Zdefault_subdomainZbind_to_environrrkbind)rCr"rJr=r=r>create_url_adaptercs       zFlask.create_url_adaptercCsw|jjdf}d|krU|jddd}t||jj|f}x|D]}|||q\WdS)zInjects the URL defaults for the given endpoint directly into the values dictionary passed. This is used internally and automatically called on URL building. .. versionadded:: 0.7 N.rr)rurrsplitr)rCr^valuesrrrr=r=r>inject_url_defaultss   zFlask.inject_url_defaultsc Cstj\}}}xe|jD]Z}y&||||}|dk rJ|SWqtk rx} z | }WYdd} ~ XqXqW||krt||||dS)zIHandle :class:`~werkzeug.routing.BuildError` on :meth:`url_for`. N)rrrnrr) rCr+r^rPr r!r"rrrr=r=r>handle_url_build_errors  zFlask.handle_url_build_errorcCstjjj}|jjdf}|dk rU||jkrUt||j|}x!|D]}|tjtjq\W|j jdf}|dk r||j krt||j |}x'|D]}|}|dk r|SqWdS)aCalled before the request is dispatched. Calls :attr:`url_value_preprocessors` registered with the app and the current blueprint (if any). Then calls :attr:`before_request_funcs` registered with the app and the blueprint. If any :meth:`before_request` handler returns a non-None value, the value is handled as if it was the return value from the view, and further request handling is stopped. N) r rr"rrtrrr^r2ro)rCrrrrr=r=r>r6s     zFlask.preprocess_requestcCstj}|jj}|j}|dk rU||jkrUt|t|j|}d|jkrt|t|jd}x|D]}||}qW|jj |j s|jj ||j ||S)aCan be overridden in order to modify the response object before it's sent to the WSGI server. By default this will call all the :meth:`after_request` decorated functions. .. versionchanged:: 0.5 As of Flask 0.5 the functions registered for after request execution are called in reverse order of registration. :param response: a :attr:`response_class` object. :return: a new response object or the same, has to be an instance of :attr:`response_class`. N) r rr"rZ_after_request_functionsrqrreversedrZis_null_sessionr#r)rCrctxrrrr=r=r>r9s    zFlask.process_responsecCs|tkrtjd}t|jjdf}tjjj }|dk r}||jkr}t |t|j|}x|D]}||qWt j |d|dS)a2Called after the request is dispatched and the response is returned, right before the request context is popped. This calls all functions decorated with :meth:`teardown_request`, and :meth:`Blueprint.teardown_request` if a blueprint handled the request. Finally, the :data:`request_tearing_down` signal is sent. This is called by :meth:`RequestContext.pop() `, which may be delayed during testing to maintain access to resources. :param exc: An unhandled exception raised while dispatching the request. Detected from the current exception information if not passed. Passed to each teardown function. .. versionchanged:: 0.9 Added the ``exc`` argument. rNexc) _sentinelrrrSrrrr rr"rrr4r&)rCrUrrrr=r=r>do_teardown_requests  zFlask.do_teardown_requestcCsW|tkrtjd}x!t|jD]}||q,Wtj|d|dS)aCalled right before the application context is popped. When handling a request, the application context is popped after the request context. See :meth:`do_teardown_request`. This calls all functions decorated with :meth:`teardown_appcontext`. Then the :data:`appcontext_tearing_down` signal is sent. This is called by :meth:`AppContext.pop() `. .. versionadded:: 0.9 rrUN)rVrrrSrsr0r&)rCrUrr=r=r>do_teardown_appcontexts  zFlask.do_teardown_appcontextcCs t|S)aFCreate an :class:`~flask.ctx.AppContext`. Use as a ``with`` block to push the context, which will make :data:`current_app` point at this application. An application context is automatically pushed by :meth:`RequestContext.push() ` when handling a request, and when running a CLI command. Use this to manually create a context outside of these situations. :: with app.app_context(): init_db() See :doc:`/appcontext`. .. versionadded:: 0.9 )r)rCr=r=r> app_context szFlask.app_contextcCs t||S)a$Create a :class:`~flask.ctx.RequestContext` representing a WSGI environment. Use a ``with`` block to push the context, which will make :data:`request` point at this request. See :doc:`/reqcontext`. Typically you should not call this from your own code. A request context is automatically pushed by the :meth:`wsgi_app` when handling a request. Use :meth:`test_request_context` to create an environment and context instead of this method. :param environ: a WSGI environment )r)rCrr=r=r>request_context) szFlask.request_contextc OsKddlm}||||}z|j|jSWd|jXdS)aCreate a :class:`~flask.ctx.RequestContext` for a WSGI environment created from the given values. This is mostly useful during testing, where you may want to run a function that uses request data without dispatching a full request. See :doc:`/reqcontext`. Use a ``with`` block to push the context, which will make :data:`request` point at the request for the created environment. :: with test_request_context(...): generate_report() When using the shell, it may be easier to push and pop the context manually to avoid indentation. :: ctx = app.test_request_context(...) ctx.push() ... ctx.pop() Takes the same arguments as Werkzeug's :class:`~werkzeug.test.EnvironBuilder`, with some defaults from the application. See the linked Werkzeug docs for most of the available arguments. Flask-specific behavior is listed here. :param path: URL path being requested. :param base_url: Base URL where the app is being served, which ``path`` is relative to. If not given, built from :data:`PREFERRED_URL_SCHEME`, ``subdomain``, :data:`SERVER_NAME`, and :data:`APPLICATION_ROOT`. :param subdomain: Subdomain name to append to :data:`SERVER_NAME`. :param url_scheme: Scheme to use instead of :data:`PREFERRED_URL_SCHEME`. :param data: The request body, either as a string or a dict of form keys and values. :param json: If given, this is serialized as JSON and passed as ``data``. Also defaults ``content_type`` to ``application/json``. :param args: other positional arguments passed to :class:`~werkzeug.test.EnvironBuilder`. :param kwargs: other keyword arguments passed to :class:`~werkzeug.test.EnvironBuilder`. r)EnvironBuilderN)rr[rZZ get_environclose)rCrDrEr[Zbuilderr=r=r>test_request_context9 s /zFlask.test_request_contextcCs|j|}d}zy|j|j}WnTtk rn}z|}|j|}WYdd}~Xntjd}YnX|||SWd|j|rd}|j|XdS)aThe actual WSGI application. This is not implemented in :meth:`__call__` so that middlewares can be applied without losing a reference to the app object. Instead of doing this:: app = MyMiddleware(app) It's a better idea to do this instead:: app.wsgi_app = MyMiddleware(app.wsgi_app) Then you still have the original application object around and can continue to call methods on it. .. versionchanged:: 0.7 Teardown events for the request and app contexts are called even if an unhandled error occurs. Other events may not be called depending on when an error occurs during dispatch. See :ref:`callbacks-and-errors`. :param environ: A WSGI environment. :param start_response: A callable accepting a status code, a list of headers, and an optional exception context to start the response. Nr) rZpushr7rr*rrr=Zauto_pop)rCrstart_responserTr+rrr=r=r>wsgi_appq s  !zFlask.wsgi_appcCs|j||S)zThe WSGI server calls the Flask application object as the WSGI application. This calls :meth:`wsgi_app` which can be wrapped to applying middleware.)r`)rCrr_r=r=r>__call__ szFlask.__call__cCsd|jj|jfS)Nz<%s %r>) __class__rr)rCr=r=r>__repr__ szFlask.__repr__){r __module__ __qualname____doc__r8Z request_classr9rr7rrZapp_ctx_globals_classrrrrZ secret_keyZsession_cookie_namer?Zpermanent_session_lifetimeZsend_file_max_age_defaultZuse_x_sendfiler JSONEncoderZ json_encoder JSONDecoderZ json_decoderrrrrrrrrzrrr/rrr\r]rar+rpropertyrrrrrrjrdrrsetterrrrrrrr@rrrrrrrHrrrrr^ staticmethodrrrrrrrrr rr r r r rrrrrrrrr#r*r'r0r4r7r(r5r1r=r8rMrQrRr6r9rVrWrXrYrZr]r`rarcr=r=r=r>rIgs* a                #   l8    $ i %     '!   ! # + ;      v &       8 + rI)Srfrerrdatetimer functoolsr itertoolsr threadingrZwerkzeug.datastructuresrrZwerkzeug.exceptionsrr r r r r Zwerkzeug.routingrrrrrZwerkzeug.wrappersrrr_compatrrrrrkrrrTrrrrr r!r"r#helpersr$r%r&r'r(r)r*r+r,r-loggingr.sessionsr/Zsignalsr0r1r2r3r4Z templatingr5r6r7Zwrappersr8r9objectrVr?rHrIr=r=r=r> s|