d
lmZej6rddlmZe<1E>Zej@dejBdejDf<00><11>Z#ej@dejHejD<00><11>Z%ej@dejL<00><11>Z'ej@dejP<00><11>Z)ej@dejT<00><11>Z+ej@dejX<00><11>Z-ej@dej\<00><11>Z/ej@dej`<00><11>Z1ej@dejd<00><11>Z3d d<1A>Z4Gd<1B>d<1C>Z5d!d<1D>Z6d"d<1E>Z7d#d<1F>Z8y)$<24>)<01>annotationsN)<01>defaultdict)<01>update_wrapper)<01>
d)d<10><04>Zejd,d<11><04>Zed-d<12><04>Zd.d<13>Zed/d<14><04>Zed/d<15><04>Zed/d<16><04>Zed/d<17><04>Zed/d<18><04>Zed/d<19><04>Zed0 d1d<1A><05>Zed2d<1B><04>Zed3d<1C><04>Zed4d<1D><04>Zed5d<1E><04>Zed6d<1F><04>Zed7d <20><04>Zed8d!<21><04>Z ed9d"<22><04>Z!ed:d#<23><04>Z"e# d;d$<24><04>Z$y)<r&a<>Common behavior shared between :class:`~flask.Flask` and
:class:`~flask.blueprints.Blueprint`.
:param import_name: The import name of the module where this object
is defined. Usually :attr:`__name__` should be used.
:param static_folder: Path to a folder of static files to serve.
If this is set, a static route will be added.
:param static_url_path: URL prefix for the static route.
:param template_folder: Path to a folder containing template files.
for rendering. If this is set, a Jinja loader will be added.
:param root_path: The path that static, template, and resource files
are relative to. Typically not set, it is discovered based on
<10><1E><1E>*<2A><15>7<EFBFBD>7<EFBFBD><<3C><<3C><04><0E><0E><04>0C<30>0C<30>D<>D<>r%c<01>^<00>|<01>$tj|<01>jd<01>}||_y)Nz\/)rS<00>fspath<74>rstripr2<00>r<00>values r#r:zScaffold.static_folder<65>s)<00><00><10><1C><16>I<EFBFBD>I<EFBFBD>e<EFBFBD>$<24>+<2B>+<2B>E<EFBFBD>2<>E<EFBFBD>#<23><04>r%c<01><00>|jduS)zQ``True`` if :attr:`static_folder` is set.
.. versionadded:: 0.5
N)r:rMs r#<00>has_static_folderzScaffold.has_static_folder<65>s<00><00><14>!<21>!<21><14>-<2D>-r%c<01><><00>|j<00>|jS|j<00>=tjj |j<00>}d|<01><00>jd<02>Sy)z<>The URL prefix that the static route will be accessible from.
If it was not configured during init, it is derived from
|j<00><00>Sy)z<>The Jinja loader for this object's templates. By default this
is a class :class:`jinja2.loaders.FileSystemLoader` to
:attr:`template_folder` if it is set.
.. versionadded:: 0.5
N)r<rrSrTrUr=rMs r#<00>jinja_loaderzScaffold.jinja_loaders7<00><00><10><1F><1F>+<2B>#<23>B<EFBFBD>G<EFBFBD>G<EFBFBD>L<EFBFBD>L<EFBFBD><14><1E><1E><14>AU<41>AU<41>$V<>W<>W<>r%c<01>L<00>d|vrtd<02><00>|j|fd|gi|<03><01>S)N<>methodsz8Use the 'route' decorator to use the 'methods' argument.)<02> TypeError<6F>route)r<00>method<6F>rule<6C>optionss r#<00>
_method_routezScaffold._method_routes5<00><00><15><07><1F><1B>V<>W<>W<><19>t<EFBFBD>z<EFBFBD>z<EFBFBD>$<24><<3C><16><08><<3C>G<EFBFBD><<3C><r%c<01>(<00>|jd||<02>S)z\Shortcut for :meth:`route` with ``methods=["GET"]``.
.. versionadded:: 2.0
<20>GET<45>rj<00>rrhris r#<00>getzScaffold.get'<00><00><00><14>!<21>!<21>%<25><14>w<EFBFBD>7<>7r%c<01>(<00>|jd||<02>S)z]Shortcut for :meth:`route` with ``methods=["POST"]``.
.. versionadded:: 2.0
<20>POSTrmrns r#<00>postz
Scaffold.post/s<00><00><14>!<21>!<21>&<26>$<24><07>8<>8r%c<01>(<00>|jd||<02>S)z\Shortcut for :meth:`route` with ``methods=["PUT"]``.
.. versionadded:: 2.0
<20>PUTrmrns r#<00>putzScaffold.put7rpr%c<01>(<00>|jd||<02>S)z_Shortcut for :meth:`route` with ``methods=["DELETE"]``.
.. versionadded:: 2.0
<20>DELETErmrns r#<00>deletezScaffold.delete?s<00><00><14>!<21>!<21>(<28>D<EFBFBD>'<27>:<3A>:r%c<01>(<00>|jd||<02>S)z^Shortcut for :meth:`route` with ``methods=["PATCH"]``.
.. versionadded:: 2.0
<20>PATCHrmrns r#<00>patchzScaffold.patchGs<00><00><14>!<21>!<21>'<27>4<EFBFBD><17>9<>9r%c<01><00><00><01><02>d<02><02><01>fd<01>}|S)a<>Decorate a view function to register it with the given URL
rule and options. Calls :meth:`add_url_rule`, which has more
details about the implementation.
.. code-block:: python
@app.route("/")
def index():
return "Hello, World!"
See :ref:`url-route-registrations`.
The endpoint name for the route defaults to the name of the view
function if the ``endpoint`` parameter isn't passed.
The ``methods`` parameter defaults to ``["GET"]``. ``HEAD`` and
<19>r%c<01><00>t<00>)a;Register a rule for routing incoming requests and building
URLs. The :meth:`route` decorator is a shortcut to call this
with the ``view_func`` argument. These are equivalent:
.. code-block:: python
@app.route("/")
def index():
...
.. code-block:: python
def index():
...
app.add_url_rule("/", view_func=index)
See :ref:`url-route-registrations`.
The endpoint name for the route defaults to the name of the view
function if the ``endpoint`` parameter isn't passed. An error
will be raised if a function has already been registered for the
endpoint.
The ``methods`` parameter defaults to ``["GET"]``. ``HEAD`` is
always added automatically, and ``OPTIONS`` is added
automatically by default.
``view_func`` does not necessarily need to be passed, but if the
rule should participate in routing an endpoint name must be
associated with a view function at some point with the
:meth:`endpoint` decorator.
.. code-block:: python
app.add_url_rule("/", endpoint="index")
@app.endpoint("index")
def index():
...
If ``view_func`` has a ``required_methods`` attribute, those
methods are added to the passed and automatic methods. If it
has a ``provide_automatic_methods`` attribute, it is used as the
default if the parameter is not passed.
:param rule: The URL rule string.
:param endpoint: The endpoint name to associate with the rule
and view function. Used when routing and building URLs.
Defaults to ``view_func.__name__``.
:param view_func: The view function to associate with the
endpoint name.
:param provide_automatic_options: Add the ``OPTIONS`` method and
respond to ``OPTIONS`` requests automatically.
:param options: Extra options passed to the
:class:`~werkzeug.routing.Rule` object.
rP)rrhr<00> view_func<6E>provide_automatic_optionsris r#r<>zScaffold.add_url_ruleos<00><00>D"<22>!r%c<01><00><00><01>d<02><01>fd<01>}|S)a<>Decorate a view function to register it for the given
endpoint. Used if a rule is added without a ``view_func`` with
:meth:`add_url_rule`.
.. code-block:: python
app.add_url_rule("/ex", endpoint="example")
@app.endpoint("example")
def example():
...
:param endpoint: The endpoint name to associate with the view
function.
c<01>&<00><02>|<00>j<00><|Sr)r>)r!rrs<20><>r#r<>z$Scaffold.endpoint.<locals>.decorator<6F>s<00><><00>,-<2D>D<EFBFBD><1F><1F><08>)<29><14>Hr%<00>r!rr(rr7)rrr<>s`` r#rzScaffold.endpoint<6E>s<00><><00>$<15><19>r%c<01>\<00>|jjdg<00>j|<01>|S)a<>Register 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.
.. code-block:: python
@app.before_request
def load_user():
if "user_id" in session:
g.user = db.session.get(session["user_id"])
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.
This is available on both app and blueprint objects. When used on an app, this
executes before every request. When used on a blueprint, this executes before
every request that the blueprint handles. To register with a blueprint and
execute before every request, use :meth:`.Blueprint.before_app_request`.
N)rA<00>
setdefault<EFBFBD>append<6E>rr!s r#<00>before_requestzScaffold.before_request<73>s*<00><00>0<0A>!<21>!<21>,<2C>,<2C>T<EFBFBD>2<EFBFBD>6<>=<3D>=<3D>a<EFBFBD>@<40><10>r%c<01>\<00>|jjdg<00>j|<01>|S)aWRegister a function to run after each request to this object.
The function is called with the response object, and must return
a response object. This allows the functions to modify or
replace the response before it is sent.
If a function raises an exception, any remaining
``after_request`` functions will not be called. Therefore, this
should not be used for actions that must execute, such as to
close resources. Use :meth:`teardown_request` for that.
This is available on both app and blueprint objects. When used on an app, this
executes after every request. When used on a blueprint, this executes after
every request that the blueprint handles. To register with a blueprint and
execute after every request, use :meth:`.Blueprint.after_app_request`.
N)rBr<>r<>r<>s r#<00>
after_requestzScaffold.after_request<73>s*<00><00>$<0A><20><20>+<2B>+<2B>D<EFBFBD>"<22>5<><<3C><<3C>Q<EFBFBD>?<3F><10>r%c<01>\<00>|jjdg<00>j|<01>|S)aRegister a function to be called when the request context is
popped. Typically this happens at the end of each request, but
contexts may be pushed manually as well during testing.
.. code-block:: python
with app.test_request_context():
...
When the ``with`` block exits (or ``ctx.pop()`` is called), the
teardown functions are called just before the request context is
made inactive.
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.
This is available on both app and blueprint objects. When used on an app, this
executes after every request. When used on a blueprint, this executes after
every request that the blueprint handles. To register with a blueprint and
execute after every request, use :meth:`.Blueprint.teardown_app_request`.
N)rCr<>r<>r<>s r#<00>teardown_requestzScaffold.teardown_request<73>s*<00><00>><0A>#<23>#<23>.<2E>.<2E>t<EFBFBD>R<EFBFBD>8<>?<3F>?<3F><01>B<><10>r%c<01>B<00>|jdj|<01>|S)a#Registers a template context processor function. These functions run before
rendering a template. The keys of the returned dict are added as variables
available in the template.
This is available on both app and blueprint objects. When used on an app, this
is called for every rendered template. When used on a blueprint, this is called
for templates rendered from the blueprint's views. To register with a blueprint
and affect every template, use :meth:`.Blueprint.app_context_processor`.
N)rDr<>r<>s r#<00>context_processorzScaffold.context_processors"<00><00><0A>(<28>(<28><14>.<2E>5<>5<>a<EFBFBD>8<><10>r%c<01>B<00>|jdj|<01>|S)alRegister 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.
This is available on both app and blueprint objects. When used on an app, this
is called for every request. When used on a blueprint, this is called for
requests that the blueprint handles. To register with a blueprint and affect
every request, use :meth:`.Blueprint.app_url_value_preprocessor`.
N)rEr<>r<>s r#<00>url_value_preprocessorzScaffold.url_value_preprocessor.s"<00><00>,<0A>$<24>$<24>T<EFBFBD>*<2A>1<>1<>!<21>4<><10>r%c<01>B<00>|jdj|<01>|S)a<>Callback 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.
This is available on both app and blueprint objects. When used on an app, this
is called for every request. When used on a blueprint, this is called for
requests that the blueprint handles. To register with a blueprint and affect
every request, use :meth:`.Blueprint.app_url_defaults`.
N)rFr<>r<>s r#<00>url_defaultszScaffold.url_defaultsGs"<00><00><0A>"<22>"<22>4<EFBFBD>(<28>/<2F>/<2F><01>2<><10>r%c<01><00><00><01>d<02><01>fd<01>}|S)a<>Register 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
This is available on both app and blueprint objects. When used on an app, this
can handle errors from every request. When used on a blueprint, this can handle
errors from requests that the blueprint handles. To register with a blueprint
and affect every request, use :meth:`.Blueprint.app_errorhandler`.
.. 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
:param code_or_exception: the code as integer for the handler, or
an arbitrary exception
c<01>,<00><02><00>j<00>|<00>|Sr)<01>register_error_handler)r!<00>code_or_exceptionrs<20><>r#r<>z(Scaffold.errorhandler.<locals>.decorator{s<00><><00><10>'<27>'<27>(9<>1<EFBFBD>=<3D><14>Hr%)r!rr(rr7)rr<>r<>s`` r#<00>errorhandlerzScaffold.errorhandlerUs<00><><00>L<15><19>r%c<01>V<00>|j|<01>\}}||jd||<y)z<>Alternative error attach function to the :meth:`errorhandler`
decorator that is more straightforward to use for non decorator
<00>st d|j<00>d<05><03><00>t|t<00>r||jfS|dfS#t$rt d|<00>d<02><03>d<03>wxYw)aGet 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.
<20>'z^' is not a recognized HTTP error code. Use a subclass of HTTPException with that code instead.Nzh is an instance, not a class. Handlers can only be registered for Exception classes or HTTP error codes.zl' is not a subclass of Exception. Handlers can only be registered for Exception classes or HTTP error codes.)<0B>
<0E>;<3B><11>;<3B><12>)#<23>0<>)#<23> +<2B>)#<23><12>)#r%r&c<01>,<00>|<00>Jd<01><00>|jS)zsInternal helper that returns the default endpoint for a given
function. This always is the function name.
z/expected view func if endpoint is not provided.)r))r<>s r#<00>_endpoint_from_view_funcr<63><00>s"<00><00><15><20>S<>"S<>S<><20><14><1D><1D>r%c<01>v<00><06>|jd<01>\}}}tjj|<01>}|<03>t d<02><00>|j<00>r|j<00>|jdk(r<>tjj|<00>}|<04>g|jr[tjtjj|j<00><00><00>t<00>fd<04>|jD<00><00>}n|jd}tjj|<05>Stjjtjj|j<00><00>Stjj|j<00>S#t
tf$rt
j<00>cYSwxYw)z2Find the path that contains the package or module.<2E>.z not found<6E> namespacec3<01>D<00>K<00>|]}<01>j|<01>r|<01><01><00>y<00>wr)<01>is_relative_to)<03>.0<EFBFBD>location<6F>package_paths<20>r#<00> <genexpr>z%_find_package_path.<locals>.<genexpr><3E>s'<00><><00><><00>'<12>$H<><08>#<23>2<>2<>8<EFBFBD><<3C><1D>$H<>s<00>r)<10> partition<6F> importlib<69>util<69> find_specr<63><00>ImportErrorrS<00>getcwd<77>submodule_search_locations<6E>origin<69>pathlib<69>PathrT<00>
<00>}t
j|<01>j|<02>r||fStjj|<01>\}}|j<00>dk(r<>tjj|<03>\}}|j<00>dk(r||fStjj|<05>j<00>dk(r!tjj|<05>|fS||fSd|fS)aFind the prefix that a package is installed under, and the path
that it would be imported from.
The prefix is the directory containing the standard directory
hierarchy (lib, bin, etc.). If the package is not installed to the
system (:attr:`sys.prefix`) or a virtualenv (``site-packages``),
``None`` is returned.
The path is the entry in :attr:`sys.path` that contains the package
for import. If the package is not installed, it's assumed that the
package was imported from the current working directory.
z
site-packages<65>libN)
r<>rSrT<00>abspath<74>sys<79>prefixr<78><00>PurePathr<68><00>split<69>lowerr_r<>)r9r<><00> py_prefix<69>site_parent<6E>site_folder<65>parent<6E>folders r#<00>find_packager<65><00>s<><00><00>&<26>k<EFBFBD>2<>L<EFBFBD><12><07><07><0F><0F><03>
