0h0SSKJr SSKJr SSKrSSKrSSKrSSK r SSK J r SSK J r SSKJr SSKJr SSKJr SSKrSSKJr SS KJr SS KJr SS KJr SS KJr SS KJr SSKJr SSKJ r SSKJ!r! SSKJ"r" SSK#J$r$ SSK%J&r' SSK(J)r) SSK*J+r+ SSK*Jr, SSK-J.r. SSK-J/r/ SSK0J1r1 SSK0J2r2 SSK0J3r3 SSK0J4r4 SSK0J5r5 SSK0J6r6 SS K0J7r7 SS!K8J9r9 SS"K8J:r: SS#K8J;r; SS$K8Jr> SS&K?J@r@ SS'KAJBrB SS(KAJCrC SS)KDJErE SS*KDJFrF SS+KDJGrG SS,KDJHrH SS-KDJIrI SS.KJJKrK SS/KLJMrM SSKLJ&r& \R(aSS0KOJPrP SS1KOJQrQ SS2KRJSrS SS3KRJTrT SS4KJUrU \R"S5\,RS69rX\R"S7\,RS69rZ\R"S8\,RS69r\\R"S9\,RS69r^\R"S:\,RS69r`S>S;jra"S<S=\>5rbg)?) annotationsN) timedelta)iscoroutinefunction)chain) TracebackType)quote)Headers) ImmutableDict)BadRequestKeyError) HTTPException)InternalServerError) BuildError) MapAdapter)RequestRedirect)RoutingException)Rule)is_running_from_reloader)Response)get_host)cli)typing AppContextRequestContext)_cv_app) _cv_request) current_app)g)request) request_ctx)session)get_debug_flag)get_flashed_messages)get_load_dotenv)send_from_directory)App) _sentinel)SecureCookieSessionInterface)SessionInterface)appcontext_tearing_down)got_request_exception)request_finished)request_started)request_tearing_down) Environment)Request) StartResponse)WSGIEnvironment FlaskClientFlaskCliRunner) HeadersValueT_shell_context_processor)bound T_teardownT_template_filterT_template_globalT_template_testcHUb[U[5(aU$[US9$)N)seconds) isinstancer)values A/var/www/auris/envauris/lib/python3.13/site-packages/flask/app.py_make_timedeltarEJs# } 5)44 U ##c^^\rSrSr%Sr\"0SS_SS_SS_SS_S S_S \"S S 9_S S_SS_SS_SS_SS_SS_SS_SS_SS_SS_SS_SSSSSSSSSSSSS. E5r\r S \ S!'\ r S"\ S#'\ "5rS$\ S%'SJSKU4S&jjjrSLS'jrSMS(jrSNSOS)jjrSPSOS*jjrSQS+jrSRS,jrSSS-jrSTS.jrSUS/jrSVSWS0jjrSXSYS1jjrSZS2jrS[S3jrS\S4jrS]S5jrS^S6jrS_S7jr S`S8jr!SaSbS9jjr"S`S:jr#ScS;jr$SdS<jr%SSSSS=.SeS>jjr&SfS?jr'SgS@jr(ShSAjr)\*4SiSBjjr+\*4SiSCjjr,SjSDjr-SkSEjr.SlSFjr/SmSGjr0SmSHjr1SIr2U=r3$)nFlaskQaThe 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: The path to the root of the application files. This should only be set manually when it can't be detected automatically, such as for namespace packages. DEBUGNTESTINGFPROPAGATE_EXCEPTIONS SECRET_KEYSECRET_KEY_FALLBACKSPERMANENT_SESSION_LIFETIME)daysUSE_X_SENDFILE TRUSTED_HOSTS SERVER_NAMEAPPLICATION_ROOT/SESSION_COOKIE_NAMEr#SESSION_COOKIE_DOMAINSESSION_COOKIE_PATHSESSION_COOKIE_HTTPONLYTSESSION_COOKIE_SECURESESSION_COOKIE_PARTITIONEDSESSION_COOKIE_SAMESITEi ihttpi) SESSION_REFRESH_EACH_REQUESTMAX_CONTENT_LENGTHMAX_FORM_MEMORY_SIZEMAX_FORM_PARTSSEND_FILE_MAX_AGE_DEFAULTTRAP_BAD_REQUEST_ERRORSTRAP_HTTP_EXCEPTIONSEXPLAIN_TEMPLATE_LOADINGPREFERRED_URL_SCHEMETEMPLATES_AUTO_RELOADMAX_COOKIE_SIZEPROVIDE_AUTOMATIC_OPTIONSz type[Request] request_classztype[Response]response_classr+session_interfacec `>^ [T U]UUUUUUUUU U S9 [R"5UlURURlUR (aP[ U5U:XdS5e[R"U5m URURS3SUU 4SjS9 gg)N) import_namestatic_url_path static_folder static_host host_matchingsubdomain_matchingtemplate_folder instance_pathinstance_relative_config root_pathz-Invalid static_host/host_matching combinationz/staticc2>T"5R"S0UD6$)N)send_static_file)kwself_refs rD Flask.__init__..sxz'B'B'HR'HrF)endpointhost view_func) super__init__rAppGroupnamehas_static_folderboolweakrefref add_url_rulerp) selfrorprqrrrsrtrurvrwrxr~ __class__s @rDrFlask.__init__s #+'#'1+'%=  "<<>    ! ! $ 5 ? 5 {{4(H   ''((89! H   "rFc[RSnUcg[U[5(a[ UR 55$U$)aUsed by :func:`send_file` to determine the ``max_age`` cache value for a given file path if it wasn't passed. By default, this returns :data:`SEND_FILE_MAX_AGE_DEFAULT` from the configuration of :data:`~flask.current_app`. This defaults to ``None``, which tells the browser to use conditional requests instead of a timed cache, which is usually preferable. Note this is a duplicate of the same method in the Flask class. .. versionchanged:: 2.0 The default configuration is ``None`` instead of 12 hours. .. versionadded:: 0.9 rcN)rconfigrBrint total_seconds)rfilenamerCs rDget_send_file_max_ageFlask.get_send_file_max_agesC"""#>? = eY ' 'u**,- - rFcUR(d [S5eURU5n[[R "[ UR5XS9$)a The view function used to serve files from :attr:`static_folder`. A route is automatically registered for this view at :attr:`static_url_path` if :attr:`static_folder` is set. Note this is a duplicate of the same method in the Flask class. .. versionadded:: 0.5 z2'static_folder' must be set to serve static_files.)max_age)r RuntimeErrorrr'tcaststrrq)rrrs rDr|Flask.send_static_file4sN%%ST T,,X6" FF3** +X  rFcUS;a [S5e[RRURU5nUS:Xa [ XB5$[ XBUS9$)aOpen a resource file relative to :attr:`root_path` for reading. For example, if the file ``schema.sql`` is next to the file ``app.py`` where the ``Flask`` app is defined, it can be opened with: .. code-block:: python with app.open_resource("schema.sql") as f: conn.executescript(f.read()) :param resource: Path to the resource relative to :attr:`root_path`. :param mode: Open the file in this mode. Only reading is supported, valid values are ``"r"`` (or ``"rt"``) and ``"rb"``. :param encoding: Open the file with this encoding when opening in text mode. This is ignored when opening in binary mode. .. versionchanged:: 3.1 Added the ``encoding`` parameter. >rrbrtz)Resources can only be opened for reading.rencoding) ValueErrorospathjoinrxopenrresourcemoderrs rD open_resourceFlask.open_resourceJsP. ( (HI Iww||DNNH5 4<# #D22rFc[RRURU5nSU;a [ XB5$[ XBUS9$)aOpen a resource file relative to the application's instance folder :attr:`instance_path`. Unlike :meth:`open_resource`, files in the instance folder can be opened for writing. :param resource: Path to the resource relative to :attr:`instance_path`. :param mode: Open the file in this mode. :param encoding: Open the file with this encoding when opening in text mode. This is ignored when opening in binary mode. .. versionchanged:: 3.1 Added the ``encoding`` parameter. br)rrrrvrrs rDopen_instance_resourceFlask.open_instance_resourceks=ww||D..9 $;# #D22rFc [UR5nSU;aURUS'SU;a"URSnUc URnX!S'UR "U40UD6nUR RUR[UR[[[S9 URRURS'U$)aCreate the Jinja environment based on :attr:`jinja_options` and the various Jinja-related methods of the app. Changing :attr:`jinja_options` after this will have no effect. Also adds Flask-related globals and filters to the environment. .. versionchanged:: 0.11 ``Environment.auto_reload`` set in accordance with ``TEMPLATES_AUTO_RELOAD`` configuration option. .. versionadded:: 0.5 autoescape auto_reloadrh)url_forr%rr!r#r zjson.dumps_function)dict jinja_optionsselect_jinja_autoescaperdebugjinja_environmentglobalsupdaterr%r!r#r jsondumpspolicies)roptionsrrvs rDcreate_jinja_environmentFlask.create_jinja_environmentst))* w &$($@$@GL !  '++&=>K""jj %0M "  # #D 4G 4 LL!5;;  .2YY__ )* rFc.UbURS=nbX!l[URUR5UlSnURSnUR R (aSnO0UR(dUR R=(d SnUR RURXCS9$URSbBUR RURSURSURSS9$g) awCreates 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. .. versionchanged:: 3.1 If :data:`SERVER_NAME` is set, it does not restrict requests to only that domain, for both ``subdomain_matching`` and ``host_matching``. .. versionchanged:: 1.0 :data:`SERVER_NAME` no longer implicitly enables subdomain matching. Use :attr:`subdomain_matching` instead. .. versionchanged:: 0.9 This can be called outside a request when the URL adapter is created for an application context. .. versionadded:: 0.6 NrSrT) server_name subdomainrUrg) script_name url_scheme) r trusted_hostsrenvironrurl_maprsrtdefault_subdomainbind_to_environbind)rr!rrrs rDcreate_url_adapterFlask.create_url_adapters(  !%_!== J(5%$GOOW5J5JKGLI++m4K||))# ,,!LL::@b <<//[0  ;;} % 1<<$$ M* KK(:;;;'=>%  rFcUR(aI[UR[5(a*URRS;dUR S;a UReSSKJn U"U5e)aIntercept routing exceptions and possibly do something else. In debug mode, intercept a routing redirect and replace it with an error if the body will be discarded. With modern Werkzeug this shouldn't occur, since it now uses a 308 status which tells the browser to resend the method and body. .. versionchanged:: 2.1 Don't intercept 307 and 308 redirects. :meta private: :internal: >34>GETHEADOPTIONSr)FormDataRoutingRedirect)rrBrouting_exceptionrcodemethod debughelpersr)rr!rs rDraise_routing_exceptionFlask.raise_routing_exceptionsY" g77II((--;~~!;;++ +9%g..rFcPSn[(a#[U[[R55nUR 5nUHOnX@R ;dMUR UH(nUR URU5"55 M* MQ UR U5 g)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. NN)r!rreversed blueprintscopytemplate_context_processorsr ensure_sync)rcontextnamesorig_ctxrfuncs rDupdate_template_contextFlask.update_template_contexts)0 7%'*<*E<<>D777 <>. /6 9+-- +   ; ' ' OO  *+-   eDJkkoom4    "-"7"7"< G" 419t9D w4::6>4::6:t, tzz4995/ , qvvc4($ @ @ ',D #eD #s #G Gc VURnUcSSKJn U"XR4SU0UD6$)alCreates a test client for this application. For information about unit testing head over to :doc:`/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`. rr5 use_cookies)test_client_classtestingr6rl)rr kwargsclss rD test_clientFlask.test_clients>f$$ ; 3 %% 3> BH  rFc >URnUcSSKJn U"U40UD6$)zCreate 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 rr7)test_cli_runner_classrr8)rrrs rDtest_cli_runnerFlask.test_cli_runners'(( ; 64"6""rFcURcU$[U[5(aU$URU[R 5nUcU$UR U5"U5$)aHandles 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 ``HTTPException`` subclasses can be handled with a catch-all handler for the base ``HTTPException``. .. versionadded:: 0.3 )rrBr_find_error_handlerr!rrrehandlers rDhandle_http_exceptionFlask.handle_http_exceptions_* 66>H a) * *H**1g.@.@A ?H(++rFcr[U[5(a,UR(dURS(aSUl[U[ 5(a'UR U5(dURU5$URU[R5nUceURU5"U5$)aThis 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 rdT) rBr rrshow_exceptionr trap_http_exceptionrrr!rrrs rDhandle_user_exceptionFlask.handle_user_exception s" a+ , , JJ$++&?@#A  a ' '0H0H0K0K--a0 0**1g.@.@A ? (++rFc[R"5n[R"XRUS9 UR SnUcUR =(d URnU(a USULaeUeURU5 [US9nURU[R5nUbUR U5"U5nURUSS9$)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 :data:`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``. .. 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 )_async_wrapper exceptionrLr)original_exceptionT)from_error_handler)sysexc_infor-sendrrrr log_exceptionr rr!rfinalize_request)rrr* propagate server_errorrs rDhandle_exceptionFlask.handle_exception+s8<<>""48H8HTUVKK 67   2 I {aG 8$*a@ **<9K9KL  ++G4\BL$$\d$KKrFc~URRS[RS[RS3US9 g)zLogs 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 z Exception on z [])r*N)loggererrorr!rr)rr*s rDr,Flask.log_exception`s8 GLL>GNN+;1 =  rFcN[RnURbURU5 URn[ USS5(a UR S:XaUR5$URnURURUR5"S0UD6$)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`. provide_automatic_optionsFrr{) r"r!rrurl_rulegetattrrmake_default_options_response view_argsrview_functionsr)rreqruler<s rDdispatch_requestFlask.dispatch_requestos!!  ,  ( ( -\\ D5u = = i'557 7&)mm  3 3DMM BCPiPPrFcSUl[R"XRS9 UR 5nUcUR 5nURU5$![ anURU5nSnAN1SnAff=f)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 T)r%N) rr/r+rpreprocess_requestr@ Exceptionr"r-)rrrs rDfull_dispatch_requestFlask.full_dispatch_requests{#' /  6F6F G((*Bz**,$$R(( /++A.B /sAA B%A;;BcURU5nURU5n[R"XRUS9 U$![ a' U(deUR RS5 U$f=f)aGiven 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: )r%responsez?Request finalizing failed with an error while handling an error) make_responseprocess_responser.r+rrDr4r&)rrr(rHs rDr-Flask.finalize_requests|"%%b) ,,X6H  ! !%5%5   % KK ! !Q   s0A-A65A6c[RnUR5nUR5nURR U5 U$)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 )r" url_adapterallowed_methodsrlallowr)radaptermethodsrs rDr;#Flask.make_default_options_responses@))))+  "   rFcH[U5(aURU5$U$)aEnsure that the function is synchronous for WSGI workers. Plain ``def`` functions are returned as-is. ``async def`` functions are wrapped to run and wait for the response. Override this method to change how the app runs async views. .. versionadded:: 2.0 )r async_to_sync)rrs rDrFlask.ensure_syncs% t $ $%%d+ + rFcTSSKJn U"U5$![a [S5Sef=f)aReturn a sync function that will run the coroutine function. .. code-block:: python result = app.async_to_sync(func)(*args, **kwargs) Override this method to change how the app converts async code to be synchronously callable. .. versionadded:: 2.0 r)rTzAInstall Flask with the 'async' extra in order to use async views.N) asgiref.syncrT ImportErrorr)rrasgiref_async_to_syncs rDrTFlask.async_to_syncs;  K %T**  S  s'_anchor_method_scheme _externalc ^[R"S5nUbBURnURRn USSS:XaU bU U3nOUSSnUcUSLnOJ[ R"S5n U b U RnOUR S5nUc [S5eUcSnUbU(d [S5eURX5 URUUUUUS9n Ub[US S 9nU S U3n U $![a,n URX#XES9 URXU5sSn A $Sn A ff=f) aGenerate a URL to the given endpoint with the given values. This is called by :func:`flask.url_for`, and can be called directly as well. An *endpoint* is the name of a URL rule, usually added with :meth:`@app.route() `, and usually the same name as the view function. A route defined in a :class:`~flask.Blueprint` will prepend the blueprint's name separated by a ``.`` to the endpoint. In some cases, such as email messages, you want URLs to include the scheme and domain, like ``https://example.com/hello``. When not in an active request, URLs will be external by default, but this requires setting :data:`SERVER_NAME` so Flask knows what domain to use. :data:`APPLICATION_ROOT` and :data:`PREFERRED_URL_SCHEME` should also be configured as needed. This config is only used when not in an active request. Functions can be decorated with :meth:`url_defaults` to modify keyword arguments before the URL is built. If building fails for some reason, such as an unknown endpoint or incorrect values, the app's :meth:`handle_url_build_error` method is called. If that returns a string, that is returned, otherwise a :exc:`~werkzeug.routing.BuildError` is raised. :param endpoint: The endpoint name associated with the URL to generate. If this starts with a ``.``, the current blueprint name (if any) will be used. :param _anchor: If given, append this as ``#anchor`` to the URL. :param _method: If given, generate the URL associated with this method for the endpoint. :param _scheme: If given, the URL will have this scheme if it is external. :param _external: If given, prefer the URL to be internal (False) or require it to be external (True). External URLs include the scheme and domain. When not in an active request, URLs are external by default. :param values: Values to use for the variable parts of the URL rule. Unknown keys are appended as query string arguments, like ``?a=b&c=d``. .. versionadded:: 2.2 Moved from ``flask.url_for``, which calls this method. Nr.zUnable to build URLs outside an active request without 'SERVER_NAME' configured. Also configure 'APPLICATION_ROOT' and 'PREFERRED_URL_SCHEME' as needed.Tz4When specifying '_scheme', '_external' must be True.)rrforce_externalr[z%!#$&'()*+,/:;=?@)safe#)rrrMr! blueprintrrrrinject_url_defaultsbuildrrhandle_url_build_error _url_quote) rrr\r]r^r_valuesreq_ctxrMblueprint_nameapp_ctxrr5s rDr Flask.url_forsr//$'  !--K$__66N|s"!-"0!1(RAU5 U$![ aOn[ US [+U5R,S 35R/[0R2"5S5SeSnAff=f) a9Convert 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`` A response object is created with the string encoded to UTF-8 as the body. ``bytes`` A response object is created with the bytes as the body. ``dict`` A dictionary that will be jsonify'd before being returned. ``list`` A list that will be jsonify'd before being returned. ``generator`` or ``iterator`` A generator that returns ``str`` or ``bytes`` to be streamed as the response. ``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:: 2.2 A generator will be converted to a streaming response. A list will be converted to a JSON response. .. versionchanged:: 1.1 A dict will be converted to a JSON response. .. 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).zThe view function for zh did not return a valid response. The function either returned None or ended without a return statement.)statusheadersz The view function did not return a valid response. The return type must be a string, dict, list, tuple with headers or status, Response instance, or WSGI callable, but it was a razThe view function did not return a valid response. The return type must be a string, dict, list, tuple with headers or status, Response instance, or WSGI callable, but it was a )!rBtuplelenr rlist TypeErrorr!rrlrbytes bytearraycabcIteratorrrH BaseResponsecallable force_typertype__name__with_tracebackr)r*rrrrr status_codersr)rrrrrslen_rvrs rDrIFlask.make_responseisMr"'+ b% WF{&(#G1begtUD%ABB"$KB!#JB ; :()9)9(<=== "1122"sE9566*R:W:W((!#) $('Bt --YY''+B --" B,,77B R))*! -VVHb !  &3y"9::" !'  JJ  g & ;!B##"#'r("3"3!4A 7 %nS\\^A%67T BBs *H I5&A I00I5cS/[[R5Q7nUHOnX R;dMURUH(nU"[R[R 5 M* MQ UHInX R ;dMUR UH"nURU5"5nUcMUs s $ MK g)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)rr!rurl_value_preprocessorsrr<before_request_funcsr)rrrurl_func before_funcrs rDrCFlask.preprocess_requests5!3!345D333 $ < `, 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. rrr%excN) r)r)r*rr!rteardown_request_funcsrrr0r+)rrrrs rDdo_teardown_requestFlask.do_teardown_request.s0 ) ,,.#C',,g6D222$T%@%@%FGD$$T*3/H7 !!$7G7GSQrFcU[La[R"5Sn[UR5HnUR U5"U5 M [ R"XR US9 g)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 rrN)r)r)r*rteardown_appcontext_funcsrr,r+)rrrs rDdo_teardown_appcontextFlask.do_teardown_appcontextPs]$ ) ,,.#CT;;` 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)rs rD app_contextFlask.app_contextjs&$rFc[X5$)aCreate 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)rrs rDrequest_contextFlask.request_contextsd,,rFcSSKJn U"U/UQ70UD6nURUR55UR 5 $!UR 5 f=f)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 app.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)EnvironBuilder)rrr get_environclose)rargsrrbuilders rDtest_request_contextFlask.test_request_contextsK^ , 777 ''(;(;(=> MMOGMMOs AAcURU5nSnUR5 UR5nU"X5SU;a<US"[R"55 US"[R"55 UbURU5(aSnURU5 $![anUnUR U5nSnANSnAf [ R "5Sne=f!SU;a<US"[R"55 US"[R"55 UbURU5(aSnURU5 f=f)a:The 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. Nrzwerkzeug.debug.preserve_context) rpushrErDr0r)r*rrrshould_ignore_errorpop)rrstart_responserr5rHrs rDwsgi_appFlask.wsgi_apps/6""7+&*   557G40G;9:7;;=I9:;??;LM T%=%=e%D%D GGEN 4003  q)1G;9:7;;=I9:;??;LM T%=%=e%D%D GGENs/ B,C/, C,6C C/C,,C//A0Ec$URX5$)zThe WSGI server calls the Flask application object as the WSGI application. This calls :meth:`wsgi_app`, which can be wrapped to apply middleware. )r)rrrs rD__call__Flask.__call__s}}W55rF)rrr) NryNFF templatesNFN)rorrp str | Nonerqstr | os.PathLike[str] | Nonerrrrsrrtrrurrvrrwrrxr)rrreturn int | None)rrrr)rN)rrrrrrrzt.IO[t.AnyStr])rzutf-8)rr1)r!zRequest | NonerzMapAdapter | None)r!r2rz t.NoReturn)rdict[str, t.Any]rNone)rr)NNNT) rrrrr bool | Nonerrrt.Anyrr)T)r rrrrr6)rrrr8)rr r&HTTPException | ft.ResponseReturnValue)rrDrr)rrDrr)r*zCtuple[type, BaseException, TracebackType] | tuple[None, None, None]rr)rft.ResponseReturnValue)rr)F)rz&ft.ResponseReturnValue | HTTPExceptionr(rrr)rt.Callable[..., t.Any]rr)rz1t.Callable[..., t.Coroutine[t.Any, t.Any, t.Any]]rr)rrr\rr]rr^rr_rrjrrr)rrrr)rzft.ResponseReturnValue | None)rHrrr)rzBaseException | Nonerr)rr)rr4rr)rrrrrr)rr4rr3rzcabc.Iterable[bytes])4r __module__ __qualname____firstlineno____doc__r rdefault_configr2rk__annotations__rrlr*rmrrr|rrrrrrrr rrrr"r0r,r@rEr-r;rrTrrIrCrJr)rrrrrrr__static_attributes__ __classcell__)rs@rDrHrHQsB^@# T u  #D  $  #D  ))*<   e  T  4    "9  $T  "4  &t  $U )%! " &t# $-1"&$+#)-'+$)(-$*%)#)-;  NH$+M=*&.NN- +G*H'H '+7?"&##(9D$(). $55$55 5  5  5!575"5#'555n6 .GK33#&39C3 3DGN33#&39C3 3,&P3j/8!8  ! y,y,y, y,  y,  y, y,v8 t#"!,!, /!,F,, /,@3Lj  V     Q2)*$) 2!  >  +E+ +8#""!%||  |  |||| ||L\6<%. R ! R  RH%.U !U U4 *- 6p0&08E0 0d6&68E6 66rFrH)rCztimedelta | int | Nonerztimedelta | None)c __future__rcollections.abcabcrzrr)rrrdatetimerinspectr itertoolsrtypesr urllib.parserrirwerkzeug.datastructuresr r werkzeug.exceptionsr r r werkzeug.routingrrrrrrrwerkzeug.wrappersrr| werkzeug.wsgirrrftrrrrrrrr r!r"r#helpersr$r%r&r' sansio.appr(sansio.scaffoldr)sessionsr*r+signalsr,r-r.r/r0 templatingr1wrappersr2 TYPE_CHECKING_typeshed.wsgir3r4rr6r8r9TypeVarShellContextProcessorCallabler:TeardownCallabler<TemplateFilterCallabler=TemplateGlobalCallabler>TemplateTestCallabler?rErHr{rFrDrsC" ', +12-3'',-!56"  #)$(&2&,*%$)#??,.$'$IIr'G'GYY|2+>+> ? II19R9RSII19R9RS))-R5L5LM$o6Co6rF