docs: :exc:TypeError

This commit is contained in:
defuz 2014-11-05 08:16:27 +03:00
parent 5562acfdfc
commit 1501b79293
5 changed files with 5 additions and 5 deletions

View file

@ -570,7 +570,7 @@ To access parameters submitted in the URL (``?key=value``) you can use the
searchword = request.args.get('key', '') searchword = request.args.get('key', '')
We recommend accessing URL parameters with `get` or by catching the We recommend accessing URL parameters with `get` or by catching the
`KeyError` because users might change the URL and presenting them a 400 :exc:`KeyError` because users might change the URL and presenting them a 400
bad request page in that case is not user friendly. bad request page in that case is not user friendly.
For a full list of methods and attributes of the request object, head over For a full list of methods and attributes of the request object, head over

View file

@ -92,7 +92,7 @@ If invalid JSON data was submitted Flask will now raise a
default :exc:`ValueError` bubble up. This has the advantage that you no default :exc:`ValueError` bubble up. This has the advantage that you no
longer have to handle that error to avoid an internal server error showing longer have to handle that error to avoid an internal server error showing
up for the user. If you were catching this down explicitly in the past up for the user. If you were catching this down explicitly in the past
as `ValueError` you will need to change this. as :exc:`ValueError` you will need to change this.
Due to a bug in the test client Flask 0.7 did not trigger teardown Due to a bug in the test client Flask 0.7 did not trigger teardown
handlers when the test client was used in a with statement. This was handlers when the test client was used in a with statement. This was

View file

@ -379,7 +379,7 @@ class Flask(_PackageBoundObject):
#: A list of functions that are called when :meth:`url_for` raises a #: A list of functions that are called when :meth:`url_for` raises a
#: :exc:`~werkzeug.routing.BuildError`. Each function registered here #: :exc:`~werkzeug.routing.BuildError`. Each function registered here
#: is called with `error`, `endpoint` and `values`. If a function #: is called with `error`, `endpoint` and `values`. If a function
#: returns ``None`` or raises a `BuildError` the next function is #: returns ``None`` or raises a :exc:`BuildError` the next function is
#: tried. #: tried.
#: #:
#: .. versionadded:: 0.9 #: .. versionadded:: 0.9

View file

@ -248,7 +248,7 @@ def url_for(endpoint, **values):
address can be changed via ``SERVER_NAME`` configuration variable which address can be changed via ``SERVER_NAME`` configuration variable which
defaults to `localhost`. defaults to `localhost`.
:param _scheme: a string specifying the desired URL scheme. The `_external` :param _scheme: a string specifying the desired URL scheme. The `_external`
parameter must be set to ``True`` or a `ValueError` is raised. The default parameter must be set to ``True`` or a :exc:`ValueError` is raised. The default
behavior uses the same scheme as the current request, or behavior uses the same scheme as the current request, or
``PREFERRED_URL_SCHEME`` from the :ref:`app configuration <config>` if no ``PREFERRED_URL_SCHEME`` from the :ref:`app configuration <config>` if no
request context is available. As of Werkzeug 0.10, this also can be set request context is available. As of Werkzeug 0.10, this also can be set

View file

@ -60,7 +60,7 @@ class JSONEncoder(_json.JSONEncoder):
def default(self, o): def default(self, o):
"""Implement this method in a subclass such that it returns a """Implement this method in a subclass such that it returns a
serializable object for ``o``, or calls the base implementation (to serializable object for ``o``, or calls the base implementation (to
raise a ``TypeError``). raise a :exc:`TypeError`).
For example, to support arbitrary iterators, you could implement For example, to support arbitrary iterators, you could implement
default like this:: default like this::