hDVxSSKJr SSKrSSKrSSKrSSKrSSKrSSKJ r SSK J r SSK Jr SSKJr SSKJr SSKJr SSKrSS KJr SS KJr SS KJr SS KJr SS KJr SSKJr SSKJr SSK J!r! SSK J"r" SSK J#r# SSK J$r$ SSK J%r% SSK J&r& SSK'J(r( SSK)J*r* SSK)J+r, SSK-J.r/ SSK0J1r1 SSK0Jr2 SSK3J4r4 SSK3J5r5 SSK6J7r7 SS K6J8r8 SS!K6J9r9 SS"K:J;r; SS#K:Jr> SS&K:J?r? SS'K:J@r@ SS(KAJBrB SS)KAJCrC SS*KAJDrD SS+KAJErE SS,KFJGrG SS-KFJHrH SS.KJIrI SS/KJJKrK SS0KJJLrL SS1KJJMrM SS2KJJNrN SS3KJJOrO SS4KPJQrQ SS5KPJRrR SS6KSJTrT SS7KSJUrU SS8KSJVrV SS9KSJWrW SS:KSJXrX SS;KYJZrZ SSK_J`r` SS?KaJbrb SS@KaJcrc \R"SA\2RSB9rf\R"SC\2RSB9rh\R"SD\2RSB9rj\R"SE\2RSB9rl\R"SF\2RSB9rnSJSGjro"SHSI\N5rpg)K) annotationsN)Iterator) timedelta)iscoroutinefunction)chain) TracebackType)quote)Headers) ImmutableDict)Aborter) BadRequest)BadRequestKeyError) HTTPException)InternalServerError) BuildError)Map) MapAdapter)RequestRedirect)RoutingException)Rule)is_running_from_reloader)cached_property)redirect)Response)cli)typing)Config)ConfigAttribute)_AppCtxGlobals AppContextRequestContext)_cv_app) _cv_request)g)request) request_ctx)session)_split_blueprint_path)get_debug_flag)get_flashed_messages)get_load_dotenv)DefaultJSONProvider) JSONProvider create_logger)_endpoint_from_view_func) _sentinel) find_package)Scaffold) setupmethod)SecureCookieSessionInterface)SessionInterface)appcontext_tearing_down)got_request_exception)request_finished)request_started)request_tearing_downDispatchingJinjaLoader) Environment)Request) Blueprint FlaskClientFlaskCliRunnerT_shell_context_processor)bound T_teardownT_template_filterT_template_globalT_template_testcHUb[U[5(aU$[US9$)N)seconds) isinstancer)values ^C:\Users\ROHAN GUPTA\OneDrive\Desktop\mathbuddy-assessment\venv\Lib\site-packages\flask/app.py_make_timedeltarSUs# } 5)44 U ##c ^\rSrSr%Sr\r\r\ r \ r \ r\r\"S5r\"S5r\"S\S9r\rS\S'0rS \S '\"0S S _SS _SS _SS _S\"SS9_SS _SS _SS_SS_SS _SS _SS_SS _SS _SS_SS _SS _S S S S S S!S".E5r\r\r S r!S#\S$'S r"S%\S&'\#"5r$S'\S('SgShU4S)jjjr%SiS*jr&\'SjS+j5r(\'SkS,j5r)\'SlS-j5r*\+SmS.j5r,SnSoS/jjr-SpS0jr.SjS1jr/SqSrS2jjr0SlS3jr1SsS4jr2StS5jr3SuS6jr4SvS7jr5\+SmS8j5r6\6RnSwS9j5r6SxSyS:jjr8SzS{S;jjr9S|S<jr:\;S}S=j5rjr=\;SSS?jj5r>\;SSS@jj5r?\;SSSAjj5r@\;SSSBjj5rA\;SSSCjj5rB\;SSSDjj5rC\;SSSEjj5rD\;SSFj5rE\;SSGj5rFSSHjrGSSIjrHSSJjrISSKjrJSSLjrKSSMjrLSSNjrMSSOjrNSSPjrOSnSSQjjrPSSRjrQSSSjrRSSTjrSSSUjrTS S S S SV.SSWjjrUSSSXjjrVSSYjrWSSZjrXSS[jrYSS\jrZSS]jr[SS^jr\\]4SS_jjr^\]4SS`jjr_SSajr`SSbjraSScjrbSSdjrcSSejrdSfreU=rf$)Flask\aThe 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. TESTING SECRET_KEYPERMANENT_SESSION_LIFETIME) get_converterztype[JSONProvider]json_provider_classdict jinja_optionsDEBUGNFPROPAGATE_EXCEPTIONS)daysUSE_X_SENDFILE SERVER_NAMEAPPLICATION_ROOT/SESSION_COOKIE_NAMEr*SESSION_COOKIE_DOMAINSESSION_COOKIE_PATHSESSION_COOKIE_HTTPONLYTSESSION_COOKIE_SECURESESSION_COOKIE_SAMESITESESSION_REFRESH_EACH_REQUESTMAX_CONTENT_LENGTHSEND_FILE_MAX_AGE_DEFAULThttpi)TRAP_BAD_REQUEST_ERRORSTRAP_HTTP_EXCEPTIONSEXPLAIN_TEMPLATE_LOADINGPREFERRED_URL_SCHEMETEMPLATES_AUTO_RELOADMAX_COOKIE_SIZEztype[FlaskClient] | Nonetest_client_classztype[FlaskCliRunner] | Nonetest_cli_runner_classr9session_interfacec >^ [T U]UUUUU S9 UcUR5nO/[RR U5(d [ S5eXlURU 5Ul UR5Ul URU5Ul /Ul/Ul/Ul0Ul0UlUR'5UlXPR(lX`lSUlUR0(aO[3U5U:XdS5e[4R6"U5m UR9UR:S3SUU 4SjS9 UR<UR>lg) N) import_name static_folderstatic_url_pathtemplate_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/staticc2>T"5R"S0UD6$)N)send_static_file)kwself_refs rR Flask.__init__..sxz'B'B'HR'HrT)endpointhost view_func) super__init__auto_find_instance_pathospathisabs ValueError instance_path make_configconfig make_aborteraborterr\jsonurl_build_error_handlersteardown_appcontext_funcsshell_context_processors blueprints extensions url_map_classurl_map host_matchingsubdomain_matching_got_first_requesthas_static_folderboolweakrefref add_url_ruler}namer) selfr{r}r| static_hostrrr~rinstance_relative_configrr __class__s @rRrFlask.__init__bs #'++     88:M}--6 + &&'?@ ((* "&":":4"@  2  %EG& QS%13!#"))+ %2 ""4#(  ! ![!]2 ?> ?2{{4(H   ''((89! H    rTcDUR(a[SUS35eg)NzThe setup method 'z' can no longer be called on the application. It has already handled its first request, any changes will not be applied consistently. Make sure all imports, decorators, functions, etc. needed to set up the application are done before running it.)rAssertionError)rf_names rR_check_setup_finishedFlask._check_setup_finisheds.  " " $VH-  #rTcURS:Xaa[[RSSS5nUcg[R R [R RU55S$UR$)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)r{getattrsysmodulesrrsplitextbasename)rfns rRr Flask.name sf   z )Z0*dCBz!77##BGG$4$4R$89!< <rTc[U5$)a3A 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 r1rs rRlogger Flask.loggers2T""rTc"UR5$)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_environmentrs rR jinja_envFlask.jinja_env5s,,..rTcLSSKnURS[SS9 UR$)zThis attribute is set to ``True`` if the application started handling the first request. .. deprecated:: 2.3 Will be removed in Flask 2.4. .. versionadded:: 0.8 rNzC'got_first_request' is deprecated and will be removed in Flask 2.4.) stacklevel)warningswarnDeprecationWarningr)rrs rRgot_first_requestFlask.got_first_request?s/  Q   &&&rTcURnU(a URn[UR5n[ 5US'UR X#5$)a4Used to create the config attribute by the Flask constructor. The `instance_relative` parameter is passed in from the constructor of Flask (there named `instance_relative_config`) and indicates if the config should be relative to the instance path or the root path of the application. .. versionadded:: 0.8 r_)rrr]default_configr, config_class)rinstance_relativerdefaultss rRrFlask.make_configRsINN **I++,*,  55rTc"UR5$)a&Create the object to assign to :attr:`aborter`. That object is called by :func:`flask.abort` to raise HTTP errors, and can be called directly as well. By default, this creates an instance of :attr:`aborter_class`, which defaults to :class:`werkzeug.exceptions.Aborter`. .. versionadded:: 2.2 ) aborter_classrs rRrFlask.make_aborterbs!!##rTc[UR5upUc [RR US5$[RR USUR S35$)zTries 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 instancevarz -instance)r5r{rrjoinr)rprefix package_paths rRrFlask.auto_find_instance_pathnsS ,D,<,<= >77<< j9 9ww||FEdii[ +BCCrTcj[[RRURU5U5$)arOpens 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'. )openrrrr)rresourcemodes rRopen_instance_resourceFlask.open_instance_resource{s&BGGLL!3!3X>EErTc [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_reloadru)url_forr-rr(r*r'zjson.dumps_function)r]r^select_jinja_autoescaperdebugjinja_environmentglobalsupdaterr-r(r*r'rdumpspolicies)roptionsrrvs rRrFlask.create_jinja_environmentst))* w &$($@$@GL !  '++&=>K""jj %0M "  # #D 4G 4 LL!5;;  .2YY__ )* rTc[U5$)ahCreates 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 r?rs rRcreate_global_jinja_loader Flask.create_global_jinja_loaders&d++rTc,UcgURS5$)zReturns ``True`` if autoescaping should be active for the given template name. If no template name is given, returns `True`. .. versionchanged:: 2.2 Autoescaping is now enabled by default for ``.svg`` files. .. versionadded:: 0.5 T)z.htmlz.htmz.xmlz.xhtmlz.svg)endswith)rfilenames rRrFlask.select_jinja_autoescapes    !LMMrTc2Sn[(a#[U[[R55nUR 5nUH@nX@R ;dMUR UHnUR U"55 M MB 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(rreversedrcopytemplate_context_processorsr)rcontextnamesorig_ctxrfuncs rRupdate_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`. rrD use_cookies)rwtestingrEresponse_class)rr*kwargsclss rR test_clientFlask.test_clients>f$$ ; 3 %% 3> BH  rTc >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 rrF)rxr+rG)rr-r.s rRtest_cli_runnerFlask.test_cli_runners'(( ; 64"6""rTc &URX5 g)aRegister 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. .. versionchanged:: 2.0.1 The ``name`` option can be used to change the (pre-dotted) name the blueprint is registered with. This allows the same blueprint to be registered multiple times with unique names for ``url_for``. .. versionadded:: 0.7 N)register)r blueprintrs rRregister_blueprintFlask.register_blueprints4 4)rTc6URR5$)zXIterates over all blueprints by the order they were registered. .. versionadded:: 0.11 )rvaluesrs rRiter_blueprintsFlask.iter_blueprintss %%''rTc Uc [U5nX%S'URSS5nUc[USS5=(d Sn[U[5(a [ S5eUVs1sHowR 5iM nn[[USS55nUc [USS5nUcSU;aS nURS5 OS nXh-nUR"U4SU0UD6nXAl URRU5 Ub@URRU5n U bX:wa[S U35eX0RU'ggs snf) Nrmethods)GETzYAllowed methods must be a list of strings, for example: @app.route(..., methods=["POST"])required_methodsrprovide_automatic_optionsOPTIONSTFzDView function mapping is overwriting an existing endpoint function: )r3poprrPr! TypeErroruppersetaddurl_rule_classrArview_functionsrr) rrulerrrArr>itemr@old_funcs rRrFlask.add_url_rulest  / :H& ++i. ?iD9EXG gs # #> -44GD::TRUTS9 U$N)r)add_template_filterfrrs rR decorator(Flask.template_filter..decorator9  $ $QT $ 2HrT)rSrKreturnrKrrrrTs`` rRtemplate_filterFlask.template_filter)s   rTcZXRRU=(d UR'g)zRegister a custom template filter. Works exactly like the :meth:`template_filter` decorator. :param name: the optional name of the filter, otherwise the function name will be used. N)rfilters__name__rrSrs rRrQFlask.add_template_filter?s67t1qzz2rTc^^SUU4SjjnU$)aA 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. c(>TRUTS9 U$rP)add_template_testrRs rRrT&Flask.template_test..decoratorbs  " "14 " 0HrT)rSrMrWrMrrXs`` rR template_testFlask.template_testKs.  rTcZXRRU=(d UR'g)zRegister a custom template test. Works exactly like the :meth:`template_test` decorator. .. versionadded:: 0.10 :param name: the optional name of the test, otherwise the function name will be used. N)rtestsr]r^s rRrbFlask.add_template_tesths45T/QZZ0rTc^^SUU4SjjnU$)awA 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. c(>TRUTS9 U$rP)add_template_globalrRs rRrT(Flask.template_global..decoratorrVrT)rSrLrWrLrrXs`` rRtemplate_globalFlask.template_globalvs$  rTcZXRRU=(d UR'g)zRegister a custom template global function. Works exactly like the :meth:`template_global` decorator. .. versionadded:: 0.10 :param name: the optional name of the global function, otherwise the function name will be used. N)rrr]r^s rRrkFlask.add_template_globals67t1qzz2rTc<URRU5 U$)aRegisters a function to be called when the application context is popped. The application context is typically popped after the request context for each request, at the end of CLI commands, or after a manually pushed context ends. .. code-block:: python with app.app_context(): ... When the ``with`` block exits (or ``ctx.pop()`` is called), the teardown functions are called just before the app context is made inactive. 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. Teardown functions must avoid raising exceptions. If they execute code that might fail they must surround that code with a ``try``/``except`` block and log any errors. The return values of teardown functions are ignored. .. versionadded:: 0.9 )rappendrrSs rRteardown_appcontextFlask.teardown_appcontexts> &&--a0rTc<URRU5 U$)zFRegisters a shell context processor function. .. versionadded:: 0.11 )rrrrss rRshell_context_processorFlask.shell_context_processors %%,,Q/rTc,UR[U55up#/[RQSP7nUbUS4OSHVnUHMnURUUnU(dMUR HnUR U5n U cMU s s s $ MO MX g)aReturn 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. Nr)_get_exc_class_and_codetyper(rerror_handler_spec__mro__r) re exc_classcodercr handler_mapr.handlers rR_find_error_handlerFlask._find_error_handlers 66tAw? +'$$+d+!%!1$w>A"55d;A> "$,,C)ooc2G*& - ?rTcURcU$[U[5(aU$URU5nUcU$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 )rrPrr ensure_syncrr~rs rRhandle_http_exceptionFlask.handle_http_exceptionsW* 66>H a) * *H**1- ?H(++rTcURS(agURSnUc'UR(a[U[5(agU(a[U[5$g)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 rrTrqF)rrrPrr )rr~trap_bad_requests rRtrap_http_exceptionFlask.trap_http_exceptionsW" ;;- .;;'@A  $ 1011 a, ,rTcT[U[5(a,UR(dURS(aSUl[U[ 5(a'UR U5(dURU5$URU5nUceURU5"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 rqT) rPrrrshow_exceptionrrrrrrs rRhandle_user_exceptionFlask.handle_user_exception&s" a+ , , JJ$++&?@#A  a ' '0H0H0K0K--a0 0**1- ? (++rTc[R"5n[R"XRUS9 UR SnUcUR =(d URnU(a USULaeUeURU5 [US9nURU5nUbUR 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 exceptionr`r)original_exceptionT)from_error_handler) rexc_infor;sendrrr+r log_exceptionrrfinalize_request)rr~r propagate server_errorrs rRhandle_exceptionFlask.handle_exceptionFs8<<>""48H8HTUVKK 67   2 I {aG 8$*a@ **<8  ++G4\BL$$\d$KKrTc~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 [])rN)rerrorr(rmethod)rrs rRrFlask.log_exception{s8 GLL>GNN+;1 =  rTcUR(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>r?HEADrBr)FormDataRoutingRedirect)rrProuting_exceptionrrr debughelpersr)rr(rs rRraise_routing_exceptionFlask.raise_routing_exceptionsY" g77II((--;~~!;;++ +9%g..rTcN[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`. rAFrBr) r)r(rrurl_rulerrmake_default_options_response view_argsrrIr)rreqrJrs rRdispatch_requestFlask.dispatch_requests!!  ,  ( ( -\\ D5u = = i'557 7&)mm  3 3DMM BCPiPPrTcSUl[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)rN) rr=rrpreprocess_requestr Exceptionrr)rrr~s rRfull_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: )rresponsez?Request finalizing failed with an error while handling an error) make_responseprocess_responser<rrrrr)rrrrs rRrFlask.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_methodsr,allowr)radapterr>rs rRr#Flask.make_default_options_responses@))))+  "   rTcg)zThis 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)rrs rRshould_ignore_errorFlask.should_ignore_errorsrTcH[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 rRrFlask.ensure_syncs% t $ $%%d+ + rTcTSSKJn 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)rzAInstall Flask with the 'async' extra in order to use async views.N) asgiref.syncr ImportError RuntimeError)rrasgiref_async_to_syncs rRrFlask.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.)r url_schemeforce_externalrz%!#$&'()*+,/:;=?@)safe#)r&rrr(r6r%create_url_adapterrrinject_url_defaultsbuildrrhandle_url_build_error _url_quote) rrrrrrr:req_ctxrblueprint_nameapp_ctxrrs rRr Flask.url_for,sp//$'  !--K$__66N|s"!-"0!1(%  rTc SnSU;a0[U[[URS5S555nUH2nX@R;dMURUH nU"X5 M M4 g)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 rrrN)rrr+ rpartitionurl_default_functions)rrr:rrrs rRrFlask.inject_url_defaultsksq)0 (?x 5h6I6I#6Nq6Q RSED111 66tI"5 CLLN1% %    s A A AAcS/[[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_preprocessorsrrbefore_request_funcsr)rrrurl_func before_funcrs rRrFlask.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. rrrexcN) r4rrrr(rteardown_request_funcsrrr>r)rrrrs rRdo_teardown_requestFlask.do_teardown_requests. ) ,,.#C',,g6D222$T%@%@%FGD$$T*3/H7 !!$7G7GSQrTcU[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)r4rrrrrr:r)rrrs rRdo_teardown_appcontextFlask.do_teardown_appcontexts]" ) ,,.#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 rR app_contextFlask.app_contexts&$rTc[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 rRrequest_contextFlask.request_context(sd,,rTcSSKJn 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)r+r%r" get_environclose)rargsr-r%builders rRtest_request_contextFlask.test_request_context8sK^ , 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) r"pushrrrrrr%rr&rrC)rrstart_responserrrr~s rRwsgi_appFlask.wsgi_appps/2""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/)rrr.s rR__call__Flask.__call__s }}W55rT) rrrrrrrrrrrrr) NrNFF templatesNFN)r{r!r} str | Noner|str | os.PathLike | Nonerr5rrrrr~r6rr5rrrr5)rr!rWNone)rWr!)rWzlogging.Logger)rWrA)rWr)F)rrrWr)rWr )rb)rr!rr!rWzt.IO[t.AnyStr])rWr@)rr!rWr)rr]rWr7)rWr])rQrrWr7)NNNT) rr5r"z int | Noner bool | Nonerrrt.AnyrWr7)T)r*rr-r:rWrE)r-r:rWrG)r6rCrr:rWr7)rWzt.ValuesView[Blueprint])NNN) rJr!rr5rzft.RouteCallable | NonerAr9rr:rWr7r)rr5rWz2t.Callable[[T_template_filter], T_template_filter])rSzft.TemplateFilterCallablerr5rWr7)rr5rWz.t.Callable[[T_template_test], T_template_test])rSzft.TemplateTestCallablerr5rWr7)rr5rWz2t.Callable[[T_template_global], T_template_global])rSzft.TemplateGlobalCallablerr5rWr7)rSrJrWrJ)rSrHrWrH)r~rrWzft.ErrorHandlerCallable | None)r~rrW&HTTPException | ft.ResponseReturnValue)r~rrWr)r~rrWr;)r~rrWr)rzCtuple[type, BaseException, TracebackType] | tuple[None, None, None]rWr7)r(rBrWz t.NoReturn)rWft.ResponseReturnValue)rWr)rz&ft.ResponseReturnValue | HTTPExceptionrrrWr)rBaseException | NonerWr)r t.CallablerWr>)rzt.Callable[..., t.Coroutine]rWzt.Callable[..., t.Any])rr!rr5rr5rr5rr9r:r:rWr!)i.)rr!rrrWr)rr<rWr)r(zRequest | NonerWzMapAdapter | None)rr!r:r]rWr7)rrrr!r:zdict[str, t.Any]rWr!)rWzft.ResponseReturnValue | None)rrrWr)rr=rWr7)rWr")rr]rWr$)r(r:r-r:rWr$)rr]r.r>rWr:)gr] __module__ __qualname____firstlineno____doc__rB request_classrr,r rrArr app_ctx_globals_classrrrr+ secret_keyrSpermanent_session_lifetimer/r\__annotations__r^r rrrrHrrrwrxr8ryrrrrrrpropertyrrrrrrrrrrrsetterr'r/r2r7r7r;rrYrQrdrbrmrkrtrwrrrrrrrrrrrrrrrrrrrrrrr4rrrr"r*r/r2__static_attributes__ __classcell__)rs@rRrVrV\s^DMNM $ +Li(G!.J"1$O"/B+A (M4# T u  #D  $  ))*<  e   4    "9  $T  "4  &t  $U  &t  +D !$! " (# $(,$)(-$*%)#/ N@N M 37/6:>6= +G*H'H '+2:"&##(4?$(). $Y"Y"$Y"0 Y"  Y"  Y"!Y"2Y""Y"#'Y"Y"Y"v   ##4//''$6 $ D F&P , N!8  $ $ \\// ! y,y,y, y,  y,  y, y,v8 t#"**6( $-115 868686+ 86 $/ 86  86 8686t!% ;*?C 7* 72< 7  7 7!% 78=A 5( 50: 5  5 5!% ;.?C 7* 72< 7  7 7B* ".!,!, /!,F!F,, /,@3Lj  V     /8Q2)*$) 2!  >  +0+ +6#""!%{{ {  {  {{{ {z OJX&P+*  +. 8H   D6:+4R'R RD+4U'U U2 *- 6p.`66rTrV)rQztimedelta | int | NonerWztimedelta | None)q __future__rloggingrrrrrcollections.abcrrdatetimerinspectr itertoolsrtypesr urllib.parser rrwerkzeug.datastructuresr r werkzeug.exceptionsr r rrrwerkzeug.routingrrrrrrrrwerkzeug.utilsrrrwerkzeug.wrappersrrrftrrrrr r"r$rr%r&r'r(r)r*helpersr+r,r-r. json.providerr/r0r2scaffoldr3r4r5r6r7sessionsr8r9signalsr:r;r<r=r> templatingr@rAwrappersrB TYPE_CHECKINGrrCr+rErGTypeVarShellContextProcessorCallablerHTeardownCallablerJTemplateFilterCallablerKTemplateGlobalCallablerLTemplateTestCallablerMrSrVrrTrRrisg" 5', +1'*2-3' ',-!5*36#  *#)$.'"."!2&,*%$).#??%$'IIr'G'GYY|2+>+> ? II19R9RSII19R9RS))-R5L5LM$I!6HI!6rT