59b0b85835
Remove apierrors.rst and errorpages.rst from patterns and integrate the content into errorhandling.rst, along with other changes and extra content.
654 lines
23 KiB
ReStructuredText
654 lines
23 KiB
ReStructuredText
Handling Application Errors
|
|
===========================
|
|
|
|
.. versionadded:: 0.3
|
|
|
|
Applications fail, servers fail. Sooner or later you will see an exception
|
|
in production. Even if your code is 100% correct, you will still see
|
|
exceptions from time to time. Why? Because everything else involved will
|
|
fail. Here are some situations where perfectly fine code can lead to server
|
|
errors:
|
|
|
|
- the client terminated the request early and the application was still
|
|
reading from the incoming data
|
|
- the database server was overloaded and could not handle the query
|
|
- a filesystem is full
|
|
- a harddrive crashed
|
|
- a backend server overloaded
|
|
- a programming error in a library you are using
|
|
- network connection of the server to another system failed
|
|
|
|
And that's just a small sample of issues you could be facing. So how do we
|
|
deal with that sort of problem? By default if your application runs in
|
|
production mode, and an exception is raised Flask will display a very simple
|
|
page for you and log the exception to the :attr:`~flask.Flask.logger`.
|
|
|
|
But there is more you can do, and we will cover some better setups to deal
|
|
with errors including custom exceptions and 3rd party tools.
|
|
|
|
|
|
.. _common-error-codes:
|
|
|
|
Common Error Codes
|
|
``````````````````
|
|
|
|
The following error codes are some that are often displayed to the user,
|
|
even if the application behaves correctly:
|
|
|
|
*400 Bad Request*
|
|
When the server will not process the request due to something that
|
|
the server perceives to be a client error. Such as malformed request
|
|
syntax, missing query parameters, etc.
|
|
|
|
*403 Forbidden*
|
|
If you have some kind of access control on your website, you will have
|
|
to send a 403 code for disallowed resources. So make sure the user
|
|
is not lost when they try to access a forbidden resource.
|
|
|
|
*404 Not Found*
|
|
The good old "chap, you made a mistake typing that URL" message. So
|
|
common that even novices to the internet know that 404 means: damn,
|
|
the thing I was looking for is not there. It's a very good idea to
|
|
make sure there is actually something useful on a 404 page, at least a
|
|
link back to the index.
|
|
|
|
*410 Gone*
|
|
Did you know that there the "404 Not Found" has a brother named "410
|
|
Gone"? Few people actually implement that, but the idea is that
|
|
resources that previously existed and got deleted answer with 410
|
|
instead of 404. If you are not deleting documents permanently from
|
|
the database but just mark them as deleted, do the user a favour and
|
|
use the 410 code instead and display a message that what they were
|
|
looking for was deleted for all eternity.
|
|
|
|
*500 Internal Server Error*
|
|
Usually happens on programming errors or if the server is overloaded.
|
|
A terribly good idea is to have a nice page there, because your
|
|
application *will* fail sooner or later.
|
|
|
|
|
|
|
|
Default Error Handling
|
|
``````````````````````
|
|
|
|
When building a Flask application you *will* run into exceptions. If some part
|
|
of your code breaks while handling a request (and you have no error handlers
|
|
registered) an "500 Internal Server Error"
|
|
(:exc:`~werkzeug.exceptions.InternalServerError`) will be returned by default.
|
|
Similarly, if a request is sent to an unregistered route a "404 Not Found"
|
|
(:exc:`~werkzeug.exceptions.NotFound`) error will occur. If a route receives an
|
|
unallowed request method a "405 Method Not Allowed"
|
|
(:exc:`~werkzeug.exceptions.MethodNotAllowed`) will be raised. These are all
|
|
subclasses of :class:`~werkzeug.exceptions.HTTPException` and are provided by
|
|
default in Flask.
|
|
|
|
Flask gives you to the ability to raise any HTTP exception registered by
|
|
werkzeug. However, as the default HTTP exceptions return simple exception
|
|
pages, Flask also offers the opportunity to customise these HTTP exceptions via
|
|
custom error handlers as well as to add exception handlers for builtin and
|
|
custom exceptions.
|
|
|
|
When an exception is caught by Flask while handling a request, it is first
|
|
looked up by code. If no handler is registered for the code, it is looked up
|
|
by its class hierarchy; the most specific handler is chosen. If no handler is
|
|
registered, :class:`~werkzeug.exceptions.HTTPException` subclasses show a
|
|
generic message about their code, while other exceptions are converted to a
|
|
generic "500 Internal Server Error".
|
|
|
|
For example, if an instance of :exc:`ConnectionRefusedError` is raised,
|
|
and a handler is registered for :exc:`ConnectionError` and
|
|
:exc:`ConnectionRefusedError`, the more specific :exc:`ConnectionRefusedError`
|
|
handler is called with the exception instance to generate the response.
|
|
|
|
Handlers registered on the blueprint take precedence over those registered
|
|
globally on the application, assuming a blueprint is handling the request that
|
|
raises the exception. However, the blueprint cannot handle 404 routing errors
|
|
because the 404 occurs at the routing level before the blueprint can be
|
|
determined.
|
|
|
|
|
|
|
|
.. _handling-errors:
|
|
|
|
Handling Errors
|
|
```````````````
|
|
|
|
Sometimes when building a Flask application, you might want to raise a
|
|
:exc:`~werkzeug.exceptions.HTTPException` to signal to the user that
|
|
something is wrong with the request. Fortunately, Flask comes with a handy
|
|
:func:`~flask.abort` function that aborts a request with a HTTP error from
|
|
werkzeug as desired.
|
|
|
|
Consider the code below, we might have a user profile route, but if the user
|
|
fails to pass a username we raise a "400 Bad Request" and if the user passes a
|
|
username but we can't find it, we raise a "404 Not Found".
|
|
|
|
.. code-block:: python
|
|
|
|
from flask import abort, render_template, request
|
|
|
|
# a username needs to be supplied in the query args
|
|
# a successful request would be like /profile?username=jack
|
|
@app.route("/profile")
|
|
def user_profile():
|
|
username = request.arg.get("username")
|
|
# if a username isn't supplied in the request, return a 400 bad request
|
|
if username is None:
|
|
abort(400)
|
|
|
|
user = get_user(username=username)
|
|
# if a user can't be found by their username, return 404 not found
|
|
if user is None:
|
|
abort(404)
|
|
|
|
return render_template("profile.html", user=user)
|
|
|
|
|
|
|
|
.. _custom-error-handlers:
|
|
|
|
Custom error handlers
|
|
`````````````````````
|
|
|
|
The default :exc:`~werkzeug.exceptions.HTTPException` returns a black and white
|
|
error page with a basic description, but nothing fancy. Considering
|
|
these errors *will* be thrown during the lifetime of your application, it is
|
|
highly advisable to customise these exceptions to improve the user experience
|
|
of your site. This can be done by registering error handlers.
|
|
|
|
An error handler is a normal view function that returns a response, but instead
|
|
of being registered for a route, it is registered for an exception or HTTP
|
|
status code that would be raised while trying to handle a request.
|
|
|
|
It is passed the instance of the error being handled, which is most
|
|
likely an integer that represents a :exc:`~werkzeug.exceptions.HTTPException`
|
|
status code. For example 500 (an "Internal Server Error") which maps to
|
|
:exc:`~werkzeug.exceptions.InternalServerError`.
|
|
|
|
It is registered with the :meth:`~flask.Flask.errorhandler`
|
|
decorator or the :meth:`~flask.Flask.register_error_handler` to register
|
|
the function later. A handler can be registered for a status code,
|
|
like 404 or 500, or for an built-in exception class, like KeyError,
|
|
or a custom exception class that inherits from Exception or its subclasses.
|
|
|
|
The status code of the response will not be set to the handler's code. Make
|
|
sure to provide the appropriate HTTP status code when returning a response from
|
|
a handler or a 200 OK HTTP code will be sent instead.
|
|
|
|
.. code-block:: python
|
|
|
|
from werkzeug.exceptions import InternalServerError
|
|
|
|
# as a decorator with an int as the exception code
|
|
@app.errorhandler(500)
|
|
def handle_internal_server_error(e):
|
|
# returning 500 with the text sets the error handler's code
|
|
# make sure to provide the appropriate HTTP status code
|
|
# otherwise 200 will be returned as default
|
|
return 'Internal Server Error!', 500
|
|
|
|
# or, as a decorator with the werkzeug exception for internal server error
|
|
@app.errorhandler(InternalServerError)
|
|
def handle_internal_server_error(e):
|
|
# werkzeug exceptions have a code attribute
|
|
return 'Internal Server Error!', e.code
|
|
|
|
# or, without the decorator
|
|
app.register_error_handler(500, handle_internal_server_error)
|
|
|
|
# similarly with a werkzeug exception
|
|
app.register_error_handler(InternalServerError, handle_internal_server_error)
|
|
|
|
|
|
|
|
A handler for "500 Internal Server Error" will not be used when running in
|
|
debug mode. Instead, the interactive debugger will be shown.
|
|
|
|
If there is an error handler registered for ``InternalServerError``,
|
|
this will be invoked. As of Flask 1.1.0, this error handler will always
|
|
be passed an instance of ``InternalServerError``, not the original
|
|
unhandled error. The original error is available as ``e.original_exception``.
|
|
Until Werkzeug 1.0.0, this attribute will only exist during unhandled
|
|
errors, use ``getattr`` to get access it for compatibility.
|
|
|
|
.. code-block:: python
|
|
|
|
@app.errorhandler(InternalServerError)
|
|
def handle_500(e):
|
|
original = getattr(e, "original_exception", None)
|
|
|
|
if original is None:
|
|
# direct 500 error, such as abort(500)
|
|
return render_template("500.html"), 500
|
|
|
|
# wrapped unhandled error
|
|
return render_template("500_unhandled.html", e=original), 500
|
|
|
|
|
|
|
|
Registering Custom Exceptions
|
|
-----------------------------
|
|
|
|
You can create your own custom exceptions by subclassing
|
|
:exc:`werkzeug.exceptions.HTTPException`. As shown above, integer HTTP codes
|
|
are interchangable when registering handlers. (``BadRequest.code == 400``)
|
|
|
|
Non-standard HTTP codes cannot be registered by code because they are not known
|
|
by Werkzeug. Instead, define a subclass of
|
|
:class:`~werkzeug.exceptions.HTTPException` with the appropriate code and
|
|
register and raise that exception class:
|
|
|
|
.. code-block:: python
|
|
|
|
class InsufficientStorage(werkzeug.exceptions.HTTPException):
|
|
code = 507
|
|
description = 'Not enough storage space.'
|
|
|
|
def handle_507(e):
|
|
return 'Not enough storage space!', 507
|
|
|
|
app.register_error_handler(InsufficientStorage, handle_507)
|
|
|
|
# during an request
|
|
raise InsufficientStorage()
|
|
|
|
Handlers can be registered for any exception class that inherits from Exception.
|
|
|
|
|
|
Unhandled Exceptions
|
|
--------------------
|
|
|
|
If an exception is raised in the code while Flask is handling a request and
|
|
there is no error handler registered for that exception, a "500 Internal Server
|
|
Error" will be returned instead. See :meth:`flask.Flask.handle_exception` for
|
|
information about this behavior.
|
|
|
|
Custom error pages
|
|
------------------
|
|
|
|
The above examples wouldn't actually be an improvement on the default
|
|
exception pages. We can create a custom 500.html template like this:
|
|
|
|
.. sourcecode:: html+jinja
|
|
|
|
{% extends "layout.html" %}
|
|
{% block title %}Internal Server Error{% endblock %}
|
|
{% block body %}
|
|
<h1>Internal Server Error</h1>
|
|
<p>Oops... we seem to have made a mistake, sorry!</p>
|
|
<p><a href="{{ url_for('index') }}">Go somewhere nice instead</a>
|
|
{% endblock %}
|
|
|
|
It can be implemented by rendering the template on "500 Internal Server Error":
|
|
|
|
.. code-block:: python
|
|
|
|
from flask import render_template
|
|
|
|
@app.errorhandler(500)
|
|
def internal_server_error(e):
|
|
# note that we set the 500 status explicitly
|
|
return render_template('500.html'), 500
|
|
|
|
|
|
When using the :doc:`/patterns/appfactories`:
|
|
|
|
.. code-block:: python
|
|
|
|
|
|
from flask import Flask, render_template
|
|
|
|
def internal_server_error(e):
|
|
return render_template('500.html'), 500
|
|
|
|
def create_app():
|
|
app = Flask(__name__)
|
|
app.register_error_handler(500, internal_server_error)
|
|
return app
|
|
|
|
|
|
When using :doc:`/blueprints`:
|
|
|
|
.. code-block:: python
|
|
|
|
from flask import Blueprint
|
|
|
|
blog = Blueprint('blog', __name__)
|
|
|
|
# as a decorator
|
|
@blog.errorhandler(500)
|
|
def internal_server_error(e):
|
|
return render_template('500.html'), 500
|
|
|
|
# or with register_error_handler
|
|
blog.register_error_handler(500, internal_server_error)
|
|
|
|
|
|
|
|
In blueprints errorhandlers will simply work as expected; however, there is a caveat
|
|
concerning handlers for 404 and 405 exceptions. These errorhandlers are only
|
|
invoked from an appropriate ``raise`` statement or a call to ``abort`` in another
|
|
of the blueprint's view functions; they are not invoked by, e.g., an invalid URL
|
|
access. This is because the blueprint does not "own" a certain URL space, so
|
|
the application instance has no way of knowing which blueprint error handler it
|
|
should run if given an invalid URL. If you would like to execute different
|
|
handling strategies for these errors based on URL prefixes, they may be defined
|
|
at the application level using the ``request`` proxy object:
|
|
|
|
.. code-block:: python
|
|
|
|
from flask import jsonify, render_template
|
|
|
|
# at the application level
|
|
# not the blueprint level
|
|
@app.errorhandler(404)
|
|
def page_not_found(e):
|
|
# if a request is in our blog URL space
|
|
if request.path.startswith('/blog/'):
|
|
# we return a custom blog 404 page
|
|
return render_template("blog/404.html"), 404
|
|
else:
|
|
# otherwise we return our generic site-wide 404 page
|
|
return render_template("404.html"), 404
|
|
|
|
|
|
@app.errorhandler(405)
|
|
def method_not_allowed(e):
|
|
# if a request has the wrong method to our API
|
|
if request.path.startswith('/api/'):
|
|
# we return a json saying so
|
|
return jsonify(message="Method Not Allowed"), 405
|
|
else:
|
|
# otherwise we return a generic site-wide 405 page
|
|
return render_template("405.html"), 405
|
|
|
|
|
|
|
|
More information on error handling with blueprint can be found in
|
|
:doc:`/blueprints`.
|
|
|
|
|
|
Returning API errors as JSON
|
|
````````````````````````````
|
|
|
|
When building APIs in Flask, some developers realise that the builtin
|
|
exceptions are not expressive enough for APIs and that the content type of
|
|
:mimetype:`text/html` they are emitting is not very useful for API consumers.
|
|
|
|
Using the same techniques as above and :func:`~flask.json.jsonify` we can return JSON
|
|
responses to API errors. :func:`~flask.abort` is called
|
|
with a ``description`` parameter. The errorhandler will
|
|
use that as the JSON error message, and set the status code to 404.
|
|
|
|
.. code-block:: python
|
|
|
|
from flask import abort, jsonify
|
|
|
|
@app.errorhandler(404)
|
|
def resource_not_found(e):
|
|
return jsonify(error=str(e)), 404
|
|
|
|
@app.route("/cheese")
|
|
def get_one_cheese():
|
|
resource = get_resource()
|
|
|
|
if resource is None:
|
|
abort(404, description="Resource not found")
|
|
|
|
return jsonify(resource)
|
|
|
|
|
|
|
|
We can also create custom exception classes; for instance, for an API we can
|
|
introduce a new custom exception that can take a proper human readable message,
|
|
a status code for the error and some optional payload to give more context
|
|
for the error.
|
|
|
|
This is a simple example:
|
|
|
|
.. code-block:: python
|
|
|
|
from flask import jsonify, request
|
|
|
|
class InvalidAPIUsage(Exception):
|
|
status_code = 400
|
|
|
|
def __init__(self, message, status_code=None, payload=None):
|
|
super().__init__()
|
|
self.message = message
|
|
if status_code is not None:
|
|
self.status_code = status_code
|
|
self.payload = payload
|
|
|
|
def to_dict(self):
|
|
rv = dict(self.payload or ())
|
|
rv['message'] = self.message
|
|
return rv
|
|
|
|
@app.errorhandler(InvalidAPIUsage)
|
|
def invalid_api_usage(e):
|
|
return jsonify(e.to_dict())
|
|
|
|
# an API app route for getting user information
|
|
# a correct request might be /api/user?user_id=420
|
|
@app.route("/api/user")
|
|
def user_api(user_id):
|
|
user_id = request.arg.get("user_id")
|
|
if not user_id:
|
|
raise InvalidAPIUsage("No user id provided!")
|
|
|
|
user = get_user(user_id=user_id)
|
|
if not user:
|
|
raise InvalidAPIUsage("No such user!", status_code=404)
|
|
|
|
return jsonify(user.to_dict())
|
|
|
|
|
|
A view can now raise that exception with an error message. Additionally
|
|
some extra payload can be provided as a dictionary through the `payload`
|
|
parameter.
|
|
|
|
|
|
Generic Exception Handlers
|
|
``````````````````````````
|
|
|
|
It is possible to register error handlers for very generic base classes
|
|
such as ``HTTPException`` or even ``Exception``. However, be aware that
|
|
these will catch more than you might expect.
|
|
|
|
An error handler for ``HTTPException`` might be useful for turning
|
|
the default HTML errors pages into JSON, for example. However, this
|
|
handler will trigger for things you don't cause directly, such as 404
|
|
and 405 errors during routing. Be sure to craft your handler carefully
|
|
so you don't lose information about the HTTP error.
|
|
|
|
.. code-block:: python
|
|
|
|
from flask import json
|
|
from werkzeug.exceptions import HTTPException
|
|
|
|
@app.errorhandler(HTTPException)
|
|
def handle_exception(e):
|
|
"""Return JSON instead of HTML for HTTP errors."""
|
|
# start with the correct headers and status code from the error
|
|
response = e.get_response()
|
|
# replace the body with JSON
|
|
response.data = json.dumps({
|
|
"code": e.code,
|
|
"name": e.name,
|
|
"description": e.description,
|
|
})
|
|
response.content_type = "application/json"
|
|
return response
|
|
|
|
# or using jsonify
|
|
@app.errorhandler(HTTPException)
|
|
def handle_exception(e):
|
|
return jsonify("code": e.code, "name": e.name, "description": e.description), e.code
|
|
|
|
|
|
An error handler for ``Exception`` might seem useful for changing how
|
|
all errors, even unhandled ones, are presented to the user. However,
|
|
this is similar to doing ``except Exception:`` in Python, it will
|
|
capture *all* otherwise unhandled errors, including all HTTP status
|
|
codes. In most cases it will be safer to register handlers for more
|
|
specific exceptions. Since ``HTTPException`` instances are valid WSGI
|
|
responses, you could also pass them through directly.
|
|
|
|
.. code-block:: python
|
|
|
|
from werkzeug.exceptions import HTTPException
|
|
|
|
@app.errorhandler(Exception)
|
|
def handle_exception(e):
|
|
# pass through HTTP errors
|
|
if isinstance(e, HTTPException):
|
|
return e
|
|
|
|
# now you're handling non-HTTP exceptions only
|
|
return render_template("500_generic.html", e=e), 500
|
|
|
|
Error handlers still respect the exception class hierarchy. If you
|
|
register handlers for both ``HTTPException`` and ``Exception``, the
|
|
``Exception`` handler will not handle ``HTTPException`` subclasses
|
|
because it the ``HTTPException`` handler is more specific.
|
|
|
|
|
|
Generic Error Pages
|
|
-------------------
|
|
|
|
If we pass in the exception into a template as below:
|
|
|
|
.. code-block:: python
|
|
|
|
from werkzeug.exceptions import HTTPException
|
|
|
|
@app.errorhandler(HTTPException)
|
|
def handle_exception(e):
|
|
return render_template("exception.html", e=e), e.code
|
|
|
|
|
|
|
|
.. sourcecode:: html+jinja
|
|
|
|
{% extends "layout.html" %}
|
|
{% block title %}{{ e.name }}{% endblock %}
|
|
{% block body %}
|
|
<h1>{{ e.code }} {{ e.name }}</h1>
|
|
<p>{{ e.description }}</p>
|
|
<p><a href="{{ url_for('index') }}">Go home</a>
|
|
{% endblock %}
|
|
|
|
|
|
|
|
Debugging Application Errors
|
|
````````````````````````````
|
|
|
|
For production applications, configure your application with logging and
|
|
notifications as described in :doc:`/logging`. This section provides
|
|
pointers when debugging deployment configuration and digging deeper with a
|
|
full-featured Python debugger.
|
|
|
|
Logging
|
|
-------
|
|
|
|
See :doc:`/logging` for information on how to log exceptions, such as by
|
|
emailing them to admins.
|
|
|
|
|
|
|
|
When in Doubt, Run Manually
|
|
---------------------------
|
|
|
|
Having problems getting your application configured for production? If you
|
|
have shell access to your host, verify that you can run your application
|
|
manually from the shell in the deployment environment. Be sure to run under
|
|
the same user account as the configured deployment to troubleshoot permission
|
|
issues. You can use Flask's builtin development server with `debug=True` on
|
|
your production host, which is helpful in catching configuration issues, but
|
|
**be sure to do this temporarily in a controlled environment.** Do not run in
|
|
production with `debug=True`.
|
|
|
|
|
|
.. _working-with-debuggers:
|
|
|
|
Working with Debuggers
|
|
----------------------
|
|
|
|
To dig deeper, possibly to trace code execution, Flask provides a debugger out
|
|
of the box (see :ref:`debug-mode`). If you would like to use another Python
|
|
debugger, note that debuggers interfere with each other. You have to set some
|
|
options in order to use your favorite debugger:
|
|
|
|
* ``debug`` - whether to enable debug mode and catch exceptions
|
|
* ``use_debugger`` - whether to use the internal Flask debugger
|
|
* ``use_reloader`` - whether to reload and fork the process if modules
|
|
were changed
|
|
|
|
``debug`` must be True (i.e., exceptions must be caught) in order for the other
|
|
two options to have any value.
|
|
|
|
If you're using Aptana/Eclipse for debugging you'll need to set both
|
|
``use_debugger`` and ``use_reloader`` to False.
|
|
|
|
A possible useful pattern for configuration is to set the following in your
|
|
config.yaml (change the block as appropriate for your application, of course)::
|
|
|
|
FLASK:
|
|
DEBUG: True
|
|
DEBUG_WITH_APTANA: True
|
|
|
|
Then in your application's entry-point (main.py),
|
|
you could have something like::
|
|
|
|
if __name__ == "__main__":
|
|
# To allow aptana to receive errors, set use_debugger=False
|
|
app = create_app(config="config.yaml")
|
|
|
|
use_debugger = app.debug and not(app.config.get('DEBUG_WITH_APTANA'))
|
|
app.run(use_debugger=use_debugger, debug=app.debug,
|
|
use_reloader=use_debugger, host='0.0.0.0')
|
|
|
|
|
|
.. _error-logging-tools:
|
|
|
|
|
|
Error Logging Tools
|
|
-------------------
|
|
|
|
Sending error mails, even if just for critical ones, can become
|
|
overwhelming if enough users are hitting the error and log files are
|
|
typically never looked at. This is why we recommend using `Sentry
|
|
<https://sentry.io/>`_ for dealing with application errors. It's
|
|
available as an Open Source project `on GitHub
|
|
<https://github.com/getsentry/sentry>`_ and is also available as a `hosted version
|
|
<https://sentry.io/signup/>`_ which you can try for free. Sentry
|
|
aggregates duplicate errors, captures the full stack trace and local
|
|
variables for debugging, and sends you mails based on new errors or
|
|
frequency thresholds.
|
|
|
|
To use Sentry you need to install the `sentry-sdk` client with extra `flask` dependencies::
|
|
|
|
$ pip install sentry-sdk[flask]
|
|
|
|
And then add this to your Flask app::
|
|
|
|
import sentry_sdk
|
|
from sentry_sdk.integrations.flask import FlaskIntegration
|
|
|
|
sentry_sdk.init('YOUR_DSN_HERE',integrations=[FlaskIntegration()])
|
|
|
|
The `YOUR_DSN_HERE` value needs to be replaced with the DSN value you get
|
|
from your Sentry installation.
|
|
|
|
After installation, failures leading to an Internal Server Error
|
|
are automatically reported to Sentry and from there you can
|
|
receive error notifications.
|
|
|
|
Follow-up reads:
|
|
|
|
* Sentry also supports catching errors from your worker queue (RQ, Celery) in a
|
|
similar fashion. See the `Python SDK docs
|
|
<https://docs.sentry.io/platforms/python/>`_ for more information.
|
|
* `Getting started with Sentry <https://docs.sentry.io/quickstart/?platform=python>`_
|
|
* `Flask-specific documentation <https://docs.sentry.io/platforms/python/flask/>`_.
|