B 5dm @sfddlZddlmZddlmZddlmZedddd d d d d gZGdddZ Gddde Z dS)N)typing) current_app)requestgetpostheadoptionsdeleteputtracepatchc@seZdZUdZdZejejeje e d<dZ ejeje e d<gZ ejejeje d<dZeje e d<ejdd d Zee ejejejd d d ZdS)ViewaSubclass this class and override :meth:`dispatch_request` to create a generic class-based view. Call :meth:`as_view` to create a view function that creates an instance of the class with the given arguments and calls its ``dispatch_request`` method with any URL variables. See :doc:`views` for a detailed guide. .. code-block:: python class Hello(View): init_every_request = False def dispatch_request(self, name): return f"Hello, {name}!" app.add_url_rule( "/hello/", view_func=Hello.as_view("hello") ) Set :attr:`methods` on the class to change what methods the view accepts. Set :attr:`decorators` on the class to apply a list of decorators to the generated view function. Decorators applied to the class itself will not be applied to the generated view function! Set :attr:`init_every_request` to ``False`` for efficiency, unless you need to store request-global data on ``self``. Nmethodsprovide_automatic_options decoratorsTinit_every_request)returncCs tdS)zThe actual view function behavior. Subclasses must override this and return a valid response. Any variables from the URL rule are passed as keyword arguments. N)NotImplementedError)selfr//tmp/pip-unpacked-wheel-qgtjwo79/flask/views.pydispatch_requestKszView.dispatch_request)name class_args class_kwargsrcs|jr$tjtjdfdd n"|tjtjdfdd |jrr|_|j_x|jD] }|qbW|_|_|j _ |j_|j _ |j _ S)afConvert the class into a view function that can be registered for a route. By default, the generated view will create a new instance of the view class for every request and call its :meth:`dispatch_request` method. If the view class sets :attr:`init_every_request` to ``False``, the same instance will be used for every request. Except for ``name``, all other arguments passed to this method are forwarded to the view class ``__init__`` method. .. versionchanged:: 2.2 Added the ``init_every_request`` class attribute. )kwargsrcsj}t|jf|S)N) view_classr ensure_syncr)rr)rrviewrrrgszView.as_view..viewcstjf|S)N)rrr)r)rrrrps) rtAnyftResponseReturnValuer__name__ __module__r__doc__rr)clsrrr decoratorr)rrrrras_viewRs    z View.as_view)r$r% __qualname__r&rr ClassVarOptional Collectionstr__annotations__rboolrListCallablerr"r#r classmethodr!Z RouteCallabler)rrrrr s   rcs>eZdZdZejddfdd ZejejdddZ Z S) MethodViewaDispatches request methods to the corresponding instance methods. For example, if you implement a ``get`` method, it will be used to handle ``GET`` requests. This can be useful for defining a REST API. :attr:`methods` is automatically set based on the methods defined on the class. See :doc:`views` for a detailed guide. .. code-block:: python class CounterAPI(MethodView): def get(self): return str(session.get("counter", 0)) def post(self): session["counter"] = session.get("counter", 0) + 1 return redirect(url_for("counter")) app.add_url_rule( "/counter", view_func=CounterAPI.as_view("counter") ) N)rrc sztjf|d|jkrvt}x&|jD]}t|ddr&||jq&Wx$tD]}t ||rL| | qLW|rv||_dS)Nr) super__init_subclass____dict__set __bases__getattrupdaterhttp_method_funcshasattraddupper)r'rrbasekey) __class__rrr6s     zMethodView.__init_subclass__cKsXt|tjd}|dkr0tjdkr0t|dd}|dk sHtdtjt|f|S)NHEADrzUnimplemented method )r:rmethodlowerAssertionErrorrr)rrmethrrrrs  zMethodView.dispatch_request) r$r%r*r&r r!r6r"r#r __classcell__rr)rBrr4sr4) rr r"globalsrr frozensetr<rr4rrrrs   z