/usr/local/lib64/python3.6/site-packages/flask/__pycache__
Edit: /usr/local/lib64/python3.6/site-packages/flask/__pycache__/views.cpython-36.pyc (4910B)
3
^TBg< @ sz d dl ZddlmZ ddlmZ ddl mZ edddd d
d d d
gZG dd dZG dd de Z
G dd dee
dZ dS ) N ) current_app)request)ResponseReturnValuegetpostheadoptionsdeleteputtracepatchc @ sp e Zd ZU dZdZejeje dZ eje
g Z ejej e
dddZeeejejej dddZdS ) Viewa Alternative way to use view functions. A subclass has to implement
:meth:`dispatch_request` which is called with the view arguments from
the URL routing system. If :attr:`methods` is provided the methods
do not have to be passed to the :meth:`~flask.Flask.add_url_rule`
method explicitly::
class MyView(View):
methods = ['GET']
def dispatch_request(self, name):
return f"Hello {name}!"
app.add_url_rule('/hello/
', view_func=MyView.as_view('myview'))
When you want to decorate a pluggable view you will have to either do that
when the view function is created (by wrapping the return value of
:meth:`as_view`) or you can use the :attr:`decorators` attribute::
class SecretView(View):
methods = ['GET']
decorators = [superuser_required]
def dispatch_request(self):
...
The decorators stored in the decorators list are applied one after another
when the view function is created. Note that you can *not* use the class
based decorators since those would decorate the view class and not the
generated view function!
N)returnc C s
t dS )zSubclasses have to override this method to implement the
actual view function code. This method is called with all
the arguments from the URL rule.
N)NotImplementedError)self r ,/tmp/pip-build-0s3hx122/flask/flask/views.pydispatch_request> s zView.dispatch_request)name
class_args class_kwargsr c sz t jt jtd fdd | jrJ|_| j_x| jD ] }|q:W | _|_| j_| j_| j_| j _ S )a Converts the class into an actual view function that can be used
with the routing system. Internally this generates a function on the
fly which will instantiate the :class:`View` on each request and call
the :meth:`dispatch_request` method on it.
The arguments passed to :meth:`as_view` are forwarded to the
constructor of the class.
)argskwargsr c s j }tj|j| |S )N)
view_classr ensure_syncr )r r r )r r viewr r r R s zView.as_view..view)
tAnyr
decorators__name__
__module__r __doc__methodsprovide_automatic_options)clsr r r Z decoratorr )r r r r as_viewE s
z View.as_view)r r! __qualname__r" r# r OptionalZListstrr$ boolr Callabler r classmethodr r& r r r r r
s
r c s e Zd ZdZ fddZ ZS )MethodViewTypezYMetaclass for :class:`MethodView` that determines what methods the view
defines.
c sx t j||| d|krtt }x$|D ] }t|dd r$|j|j q$W x$tD ] }t| |rJ|j|j qJW |rt|| _d S )Nr# )
super__init__setgetattrupdater# http_method_funcshasattraddupper)r% r basesdr# basekey) __class__r r r/ o s
zMethodViewType.__init__)r r! r' r" r/
__classcell__r r )r; r r- j s r- c @ s& e Zd ZdZejejedddZdS )
MethodViewa A class-based view that dispatches request methods to the corresponding
class methods. For example, if you implement a ``get`` method, it will be
used to handle ``GET`` requests. ::
class CounterAPI(MethodView):
def get(self):
return session.get('counter', 0)
def post(self):
session['counter'] = session.get('counter', 0) + 1
return 'OK'
app.add_url_rule('/counter', view_func=CounterAPI.as_view('counter'))
)r r r c O sX t | tjj d }|d kr0tjdkr0t | dd }|d k sHtdtjtj|||S )NHEADr zUnimplemented method )r1 r methodlowerAssertionErrorr r )r r r methr r r r s
zMethodView.dispatch_requestN)r r! r' r" r r r r r r r r r= s r= ) metaclass) Ztypingr globalsr r r frozensetr3 r typer- r= r r r r s ]