diff --git a/.appveyor.yml b/.appveyor.yml
new file mode 100644
index 00000000..3a7d2f63
--- /dev/null
+++ b/.appveyor.yml
@@ -0,0 +1,23 @@
+environment:
+ global:
+ TOXENV: py
+
+ matrix:
+ - PYTHON: C:\Python36
+ - PYTHON: C:\Python27
+
+init:
+ - SET PATH=%PYTHON%;%PATH%
+
+install:
+ - python -m pip install -U pip setuptools wheel tox
+
+build: false
+
+test_script:
+ - python -m tox
+
+branches:
+ only:
+ - master
+ - /^.*-maintenance$/
diff --git a/.coveragerc b/.coveragerc
new file mode 100644
index 00000000..b2cf1785
--- /dev/null
+++ b/.coveragerc
@@ -0,0 +1,11 @@
+[run]
+branch = True
+source =
+ flask
+ tests
+
+[paths]
+source =
+ flask
+ .tox/*/lib/python*/site-packages/flask
+ .tox/pypy/site-packages/flask
diff --git a/.github/ISSUE_TEMPLATE.md b/.github/ISSUE_TEMPLATE.md
new file mode 100644
index 00000000..8b6910fb
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE.md
@@ -0,0 +1,33 @@
+**This issue tracker is a tool to address bugs in Flask itself.
+Please use the #pocoo IRC channel on freenode or Stack Overflow for general
+questions about using Flask or issues not related to Flask.**
+
+If you'd like to report a bug in Flask, fill out the template below. Provide
+any any extra information that may be useful / related to your problem.
+Ideally, create an [MCVE](http://stackoverflow.com/help/mcve), which helps us
+understand the problem and helps check that it is not caused by something in
+your code.
+
+---
+
+### Expected Behavior
+
+Tell us what should happen.
+
+```python
+Paste a minimal example that causes the problem.
+```
+
+### Actual Behavior
+
+Tell us what happens instead.
+
+```pytb
+Paste the full traceback if there was an exception.
+```
+
+### Environment
+
+* Python version:
+* Flask version:
+* Werkzeug version:
diff --git a/.github/ISSUE_TEMPLATE.rst b/.github/ISSUE_TEMPLATE.rst
deleted file mode 100644
index 8854961a..00000000
--- a/.github/ISSUE_TEMPLATE.rst
+++ /dev/null
@@ -1,2 +0,0 @@
-The issue tracker is a tool to address bugs.
-Please use the #pocoo IRC channel on freenode or Stack Overflow for questions.
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
new file mode 100644
index 00000000..9dda856c
--- /dev/null
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -0,0 +1,16 @@
+Describe what this patch does to fix the issue.
+
+Link to any relevant issues or pull requests.
+
+
diff --git a/.gitignore b/.gitignore
index 9bf4f063..231c0873 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,4 +1,6 @@
.DS_Store
+.env
+.flaskenv
*.pyc
*.pyo
env
@@ -11,3 +13,9 @@ _mailinglist
.tox
.cache/
.idea/
+
+# Coverage reports
+htmlcov
+.coverage
+.coverage.*
+*,cover
diff --git a/.gitmodules b/.gitmodules
deleted file mode 100644
index 3d7df149..00000000
--- a/.gitmodules
+++ /dev/null
@@ -1,3 +0,0 @@
-[submodule "docs/_themes"]
- path = docs/_themes
- url = https://github.com/mitsuhiko/flask-sphinx-themes.git
diff --git a/.travis.yml b/.travis.yml
index 0f99a7e8..e156d1b3 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -1,55 +1,37 @@
sudo: false
language: python
-python:
- - "2.6"
- - "2.7"
- - "pypy"
- - "3.3"
- - "3.4"
- - "3.5"
-
-env:
- - REQUIREMENTS=lowest
- - REQUIREMENTS=lowest-simplejson
- - REQUIREMENTS=release
- - REQUIREMENTS=release-simplejson
- - REQUIREMENTS=devel
- - REQUIREMENTS=devel-simplejson
-
matrix:
- exclude:
- # Python 3 support currently does not work with lowest requirements
- - python: "3.3"
- env: REQUIREMENTS=lowest
- - python: "3.3"
- env: REQUIREMENTS=lowest-simplejson
- - python: "3.4"
- env: REQUIREMENTS=lowest
- - python: "3.4"
- env: REQUIREMENTS=lowest-simplejson
- - python: "3.5"
- env: REQUIREMENTS=lowest
- - python: "3.5"
- env: REQUIREMENTS=lowest-simplejson
-
+ include:
+ - python: 3.6
+ env: TOXENV=py,simplejson,devel,lowest,codecov,docs-html
+ - python: 3.5
+ env: TOXENV=py,codecov
+ - python: 3.4
+ env: TOXENV=py,codecov
+ - python: 2.7
+ env: TOXENV=py,simplejson,devel,lowest,codecov
+ - python: pypy
+ env: TOXENV=py,codecov
+ - python: nightly
+ env: TOXENV=py
+ allow_failures:
+ - python: nightly
+ env: TOXENV=py
install:
- - pip install tox
+ - pip install tox
script:
- - tox -e py-$REQUIREMENTS
+ - tox
+
+cache:
+ - pip
branches:
- except:
- - website
+ only:
+ - master
+ - /^.*-maintenance$/
notifications:
email: false
- irc:
- channels:
- - "chat.freenode.net#pocoo"
- on_success: change
- on_failure: always
- use_notice: true
- skip_join: true
diff --git a/AUTHORS b/AUTHORS
index cc157dc4..3237ea65 100644
--- a/AUTHORS
+++ b/AUTHORS
@@ -9,6 +9,7 @@ Development Lead
Patches and Suggestions
```````````````````````
+- Adam Byrtek
- Adam Zapletal
- Ali Afshar
- Chris Edgemon
@@ -20,7 +21,9 @@ Patches and Suggestions
- Edmond Burnett
- Florent Xicluna
- Georg Brandl
+- Hsiaoming Yang @lepture
- Jeff Widman @jeffwidman
+- Joshua Bronson @jab
- Justin Quick
- Kenneth Reitz
- Keyan Pishdadian
diff --git a/CHANGES b/CHANGES.rst
similarity index 74%
rename from CHANGES
rename to CHANGES.rst
index 13ce156c..b1b65a45 100644
--- a/CHANGES
+++ b/CHANGES.rst
@@ -1,11 +1,197 @@
Flask Changelog
===============
-Here you can see the full list of changes between each Flask release.
+
+Version 1.0
+-----------
+
+unreleased
+
+- **Python 2.6 and 3.3 are no longer supported.** (`pallets/meta#24`_)
+- Bump minimum dependency versions to the latest stable versions:
+ Werkzeug >= 0.14, Jinja >= 2.10, itsdangerous >= 0.24, Click >= 5.1.
+ (`#2586`_)
+- Make ``app.run()`` into a noop if a Flask application is run from the
+ development server on the command line. This avoids some behavior that
+ was confusing to debug for newcomers.
+- Change default configuration ``JSONIFY_PRETTYPRINT_REGULAR=False``.
+ ``jsonify()`` method returns compressed response by default, and pretty
+ response in debug mode. (`#2193`_)
+- Change ``Flask.__init__`` to accept two new keyword arguments,
+ ``host_matching`` and ``static_host``. This enables ``host_matching`` to be
+ set properly by the time the constructor adds the static route, and enables
+ the static route to be properly associated with the required host.
+ (``#1559``)
+- ``send_file`` supports Unicode in ``attachment_filename``. (`#2223`_)
+- Pass ``_scheme`` argument from ``url_for`` to ``handle_build_error``.
+ (`#2017`_)
+- Add support for ``provide_automatic_options`` in ``add_url_rule`` to disable
+ adding OPTIONS method when the ``view_func`` argument is not a class.
+ (`#1489`_).
+- ``MethodView`` can inherit method handlers from base classes. (`#1936`_)
+- Errors caused while opening the session at the beginning of the request are
+ handled by the app's error handlers. (`#2254`_)
+- Blueprints gained ``json_encoder`` and ``json_decoder`` attributes to
+ override the app's encoder and decoder. (`#1898`_)
+- ``Flask.make_response`` raises ``TypeError`` instead of ``ValueError`` for
+ bad response types. The error messages have been improved to describe why the
+ type is invalid. (`#2256`_)
+- Add ``routes`` CLI command to output routes registered on the application.
+ (`#2259`_)
+- Show warning when session cookie domain is a bare hostname or an IP
+ address, as these may not behave properly in some browsers, such as Chrome.
+ (`#2282`_)
+- Allow IP address as exact session cookie domain. (`#2282`_)
+- ``SESSION_COOKIE_DOMAIN`` is set if it is detected through ``SERVER_NAME``.
+ (`#2282`_)
+- Auto-detect zero-argument app factory called ``create_app`` or ``make_app``
+ from ``FLASK_APP``. (`#2297`_)
+- Factory functions are not required to take a ``script_info`` parameter to
+ work with the ``flask`` command. If they take a single parameter or a
+ parameter named ``script_info``, the ``ScriptInfo`` object will be passed.
+ (`#2319`_)
+- FLASK_APP=myproject.app:create_app('dev') support.
+- ``FLASK_APP`` can be set to an app factory, with arguments if needed, for
+ example ``FLASK_APP=myproject.app:create_app('dev')``. (`#2326`_)
+- ``FLASK_APP`` can point to local packages that are not installed in dev mode,
+ although `pip install -e` should still be preferred. (`#2414`_)
+- ``View.provide_automatic_options = True`` is set on the view function from
+ ``View.as_view``, to be detected in ``app.add_url_rule``. (`#2316`_)
+- Error handling will try handlers registered for ``blueprint, code``,
+ ``app, code``, ``blueprint, exception``, ``app, exception``. (`#2314`_)
+- ``Cookie`` is added to the response's ``Vary`` header if the session is
+ accessed at all during the request (and it wasn't deleted). (`#2288`_)
+- ``app.test_request_context()`` take ``subdomain`` and ``url_scheme``
+ parameters for use when building base URL. (`#1621`_)
+- Set ``APPLICATION_ROOT = '/'`` by default. This was already the implicit
+ default when it was set to ``None``.
+- ``TRAP_BAD_REQUEST_ERRORS`` is enabled by default in debug mode.
+ ``BadRequestKeyError`` has a message with the bad key in debug mode instead
+ of the generic bad request message. (`#2348`_)
+- Allow registering new tags with ``TaggedJSONSerializer`` to support
+ storing other types in the session cookie. (`#2352`_)
+- Only open the session if the request has not been pushed onto the context
+ stack yet. This allows ``stream_with_context`` generators to access the same
+ session that the containing view uses. (`#2354`_)
+- Add ``json`` keyword argument for the test client request methods. This will
+ dump the given object as JSON and set the appropriate content type.
+ (`#2358`_)
+- Extract JSON handling to a mixin applied to both the request and response
+ classes used by Flask. This adds the ``is_json`` and ``get_json`` methods to
+ the response to make testing JSON response much easier. (`#2358`_)
+- Removed error handler caching because it caused unexpected results for some
+ exception inheritance hierarchies. Register handlers explicitly for each
+ exception if you don't want to traverse the MRO. (`#2362`_)
+- Fix incorrect JSON encoding of aware, non-UTC datetimes. (`#2374`_)
+- Template auto reloading will honor the ``run`` command's ``debug`` flag even
+ if ``app.jinja_env`` was already accessed. (`#2373`_)
+- The following old deprecated code was removed. (`#2385`_)
+
+ - ``flask.ext`` - import extensions directly by their name instead of
+ through the ``flask.ext`` namespace. For example,
+ ``import flask.ext.sqlalchemy`` becomes ``import flask_sqlalchemy``.
+ - ``Flask.init_jinja_globals`` - extend ``Flask.create_jinja_environment``
+ instead.
+ - ``Flask.error_handlers`` - tracked by ``Flask.error_handler_spec``,
+ use ``@app.errorhandler`` to register handlers.
+ - ``Flask.request_globals_class`` - use ``Flask.app_ctx_globals_class``
+ instead.
+ - ``Flask.static_path`` - use ``Flask.static_url_path`` instead.
+ - ``Request.module`` - use ``Request.blueprint`` instead.
+
+- The ``request.json`` property is no longer deprecated. (`#1421`_)
+- Support passing an existing ``EnvironBuilder`` or ``dict`` to
+ ``test_client.open``. (`#2412`_)
+- The ``flask`` command and ``app.run`` will load environment variables using
+ from ``.env`` and ``.flaskenv`` files if python-dotenv is installed.
+ (`#2416`_)
+- When passing a full URL to the test client, use the scheme in the URL instead
+ of the ``PREFERRED_URL_SCHEME``. (`#2430`_)
+- ``app.logger`` has been simplified. ``LOGGER_NAME`` and
+ ``LOGGER_HANDLER_POLICY`` config was removed. The logger is always named
+ ``flask.app``. The level is only set on first access, it doesn't check
+ ``app.debug`` each time. Only one format is used, not different ones
+ depending on ``app.debug``. No handlers are removed, and a handler is only
+ added if no handlers are already configured. (`#2436`_)
+- Blueprint view function name may not contain dots. (`#2450`_)
+- Fix a ``ValueError`` caused by invalid Range requests in some cases.
+ (`#2526`_)
+- The dev server now uses threads by default. (`#2529`_)
+- Loading config files with ``silent=True`` will ignore ``ENOTDIR``
+ errors. (`#2581`_)
+- Pass ``--cert`` and ``--key`` options to ``flask run`` to run the
+ development server over HTTPS. (`#2606`_)
+- Added :data:`SESSION_COOKIE_SAMESITE` to control the ``SameSite``
+ attribute on the session cookie. (`#2607`_)
+
+.. _pallets/meta#24: https://github.com/pallets/meta/issues/24
+.. _#1421: https://github.com/pallets/flask/issues/1421
+.. _#1489: https://github.com/pallets/flask/pull/1489
+.. _#1621: https://github.com/pallets/flask/pull/1621
+.. _#1898: https://github.com/pallets/flask/pull/1898
+.. _#1936: https://github.com/pallets/flask/pull/1936
+.. _#2017: https://github.com/pallets/flask/pull/2017
+.. _#2193: https://github.com/pallets/flask/pull/2193
+.. _#2223: https://github.com/pallets/flask/pull/2223
+.. _#2254: https://github.com/pallets/flask/pull/2254
+.. _#2256: https://github.com/pallets/flask/pull/2256
+.. _#2259: https://github.com/pallets/flask/pull/2259
+.. _#2282: https://github.com/pallets/flask/pull/2282
+.. _#2288: https://github.com/pallets/flask/pull/2288
+.. _#2297: https://github.com/pallets/flask/pull/2297
+.. _#2314: https://github.com/pallets/flask/pull/2314
+.. _#2316: https://github.com/pallets/flask/pull/2316
+.. _#2319: https://github.com/pallets/flask/pull/2319
+.. _#2326: https://github.com/pallets/flask/pull/2326
+.. _#2348: https://github.com/pallets/flask/pull/2348
+.. _#2352: https://github.com/pallets/flask/pull/2352
+.. _#2354: https://github.com/pallets/flask/pull/2354
+.. _#2358: https://github.com/pallets/flask/pull/2358
+.. _#2362: https://github.com/pallets/flask/pull/2362
+.. _#2374: https://github.com/pallets/flask/pull/2374
+.. _#2373: https://github.com/pallets/flask/pull/2373
+.. _#2385: https://github.com/pallets/flask/issues/2385
+.. _#2412: https://github.com/pallets/flask/pull/2412
+.. _#2414: https://github.com/pallets/flask/pull/2414
+.. _#2416: https://github.com/pallets/flask/pull/2416
+.. _#2430: https://github.com/pallets/flask/pull/2430
+.. _#2436: https://github.com/pallets/flask/pull/2436
+.. _#2450: https://github.com/pallets/flask/pull/2450
+.. _#2526: https://github.com/pallets/flask/issues/2526
+.. _#2529: https://github.com/pallets/flask/pull/2529
+.. _#2586: https://github.com/pallets/flask/issues/2586
+.. _#2581: https://github.com/pallets/flask/pull/2581
+.. _#2606: https://github.com/pallets/flask/pull/2606
+.. _#2607: https://github.com/pallets/flask/pull/2607
+
+
+Version 0.12.2
+--------------
+
+Released on May 16 2017
+
+- Fix a bug in `safe_join` on Windows.
+
+Version 0.12.1
+--------------
+
+Bugfix release, released on March 31st 2017
+
+- Prevent `flask run` from showing a NoAppException when an ImportError occurs
+ within the imported application module.
+- Fix encoding behavior of ``app.config.from_pyfile`` for Python 3. Fix
+ ``#2118``.
+- Use the ``SERVER_NAME`` config if it is present as default values for
+ ``app.run``. ``#2109``, ``#2152``
+- Call `ctx.auto_pop` with the exception object instead of `None`, in the
+ event that a `BaseException` such as `KeyboardInterrupt` is raised in a
+ request handler.
Version 0.12
------------
+Released on December 21st 2016, codename Punsch.
+
- the cli command now responds to `--version`.
- Mimetype guessing and ETag generation for file-like objects in ``send_file``
has been removed, as per issue ``#104``. See pull request ``#1849``.
@@ -104,6 +290,8 @@ Released on May 29th 2016, codename Absinthe.
- Don't leak exception info of already catched exceptions to context teardown
handlers (pull request ``#1393``).
- Allow custom Jinja environment subclasses (pull request ``#1422``).
+- Updated extension dev guidelines.
+
- ``flask.g`` now has ``pop()`` and ``setdefault`` methods.
- Turn on autoescape for ``flask.templating.render_template_string`` by default
(pull request ``#1515``).
diff --git a/CONTRIBUTING.rst b/CONTRIBUTING.rst
index d9cd2214..ef02b732 100644
--- a/CONTRIBUTING.rst
+++ b/CONTRIBUTING.rst
@@ -1,114 +1,166 @@
-==========================
How to contribute to Flask
==========================
-Thanks for considering contributing to Flask.
+Thank you for considering contributing to Flask!
Support questions
-=================
+-----------------
+
+Please, don't use the issue tracker for this. Use one of the following
+resources for questions about your own code:
+
+* The IRC channel ``#pocoo`` on FreeNode.
+* The IRC channel ``#python`` on FreeNode for more general questions.
+* The mailing list flask@python.org for long term discussion or larger issues.
+* Ask on `Stack Overflow`_. Search with Google first using:
+ ``site:stackoverflow.com flask {search term, exception message, etc.}``
-Please, don't use the issue tracker for this. Check whether the ``#pocoo`` IRC
-channel on Freenode can help with your issue. If your problem is not strictly
-Werkzeug or Flask specific, ``#python`` is generally more active.
-`Stack Overflow `_ is also worth considering.
+.. _Stack Overflow: https://stackoverflow.com/questions/tagged/flask?sort=linked
Reporting issues
-================
+----------------
-- Under which versions of Python does this happen? This is even more important
- if your issue is encoding related.
+- Describe what you expected to happen.
+- If possible, include a `minimal, complete, and verifiable example`_ to help
+ us identify the issue. This also helps check that the issue is not with your
+ own code.
+- Describe what actually happened. Include the full traceback if there was an
+ exception.
+- List your Python, Flask, and Werkzeug versions. If possible, check if this
+ issue is already fixed in the repository.
-- Under which versions of Werkzeug does this happen? Check if this issue is
- fixed in the repository.
+.. _minimal, complete, and verifiable example: https://stackoverflow.com/help/mcve
Submitting patches
-==================
+------------------
- Include tests if your patch is supposed to solve a bug, and explain
clearly under which circumstances the bug happens. Make sure the test fails
without your patch.
+- Try to follow `PEP8`_, but you may ignore the line length limit if following
+ it would make the code uglier.
+
+First time setup
+~~~~~~~~~~~~~~~~
+
+- Download and install the `latest version of git`_.
+- Configure git with your `username`_ and `email`_::
+
+ git config --global user.name 'your name'
+ git config --global user.email 'your email'
-- Try to follow `PEP8 `_, but you
- may ignore the line-length-limit if following it would make the code uglier.
+- Make sure you have a `GitHub account`_.
+- Fork Flask to your GitHub account by clicking the `Fork`_ button.
+- `Clone`_ your GitHub fork locally::
+ git clone https://github.com/{username}/flask
+ cd flask
-Running the testsuite
----------------------
+- Add the main repository as a remote to update later::
-You probably want to set up a `virtualenv
-`_.
+ git remote add pallets https://github.com/pallets/flask
+ git fetch pallets
-The minimal requirement for running the testsuite is ``py.test``. You can
-install it with::
+- Create a virtualenv::
- pip install pytest
+ python3 -m venv env
+ . env/bin/activate
+ # or "env\Scripts\activate" on Windows
-Clone this repository::
+- Install Flask in editable mode with development dependencies::
- git clone https://github.com/pallets/flask.git
+ pip install -e ".[dev]"
-Install Flask as an editable package using the current source::
+.. _GitHub account: https://github.com/join
+.. _latest version of git: https://git-scm.com/downloads
+.. _username: https://help.github.com/articles/setting-your-username-in-git/
+.. _email: https://help.github.com/articles/setting-your-email-in-git/
+.. _Fork: https://github.com/pallets/flask/pull/2305#fork-destination-box
+.. _Clone: https://help.github.com/articles/fork-a-repo/#step-2-create-a-local-clone-of-your-fork
- cd flask
- pip install --editable .
+Start coding
+~~~~~~~~~~~~
-Then you can run the testsuite with::
+- Create a branch to identify the issue you would like to work on (e.g.
+ ``2287-dry-test-suite``)
+- Using your favorite editor, make your changes, `committing as you go`_.
+- Try to follow `PEP8`_, but you may ignore the line length limit if following
+ it would make the code uglier.
+- Include tests that cover any code changes you make. Make sure the test fails
+ without your patch. `Run the tests. `_.
+- Push your commits to GitHub and `create a pull request`_.
+- Celebrate 🎉
- py.test
+.. _committing as you go: http://dont-be-afraid-to-commit.readthedocs.io/en/latest/git/commandlinegit.html#commit-your-changes
+.. _PEP8: https://pep8.org/
+.. _create a pull request: https://help.github.com/articles/creating-a-pull-request/
-With only py.test installed, a large part of the testsuite will get skipped
-though. Whether this is relevant depends on which part of Flask you're working
-on. Travis is set up to run the full testsuite when you submit your pull
-request anyways.
+.. _contributing-testsuite:
-If you really want to test everything, you will have to install ``tox`` instead
-of ``pytest``. You can install it with::
+Running the tests
+~~~~~~~~~~~~~~~~~
- pip install tox
+Run the basic test suite with::
-The ``tox`` command will then run all tests against multiple combinations
-Python versions and dependency versions.
+ pytest
+
+This only runs the tests for the current environment. Whether this is relevant
+depends on which part of Flask you're working on. Travis-CI will run the full
+suite when you submit your pull request.
+
+The full test suite takes a long time to run because it tests multiple
+combinations of Python and dependencies. You need to have Python 2.7, 3.4,
+3.5 3.6, and PyPy 2.7 installed to run all of the environments. Then run::
+
+ tox
Running test coverage
----------------------
-Generating a report of lines that do not have unit test coverage can indicate where
-to start contributing. ``pytest`` integrates with ``coverage.py``, using the ``pytest-cov``
-plugin. This assumes you have already run the testsuite (see previous section)::
+~~~~~~~~~~~~~~~~~~~~~
- pip install pytest-cov
+Generating a report of lines that do not have test coverage can indicate
+where to start contributing. Run ``pytest`` using ``coverage`` and generate a
+report on the terminal and as an interactive HTML document::
-After this has been installed, you can output a report to the command line using this command::
+ coverage run -m pytest
+ coverage report
+ coverage html
+ # then open htmlcov/index.html
- py.test --cov=flask tests/
+Read more about `coverage `_.
-Generate a HTML report can be done using this command::
+Running the full test suite with ``tox`` will combine the coverage reports
+from all runs.
- py.test --cov-report html --cov=flask tests/
+``make`` targets
+~~~~~~~~~~~~~~~~
-Full docs on ``coverage.py`` are here: https://coverage.readthedocs.io
+Flask provides a ``Makefile`` with various shortcuts. They will ensure that
+all dependencies are installed.
-Caution
-=======
-pushing
--------
-This repository contains several zero-padded file modes that may cause issues when pushing this repository to git hosts other than github. Fixing this is destructive to the commit history, so we suggest ignoring these warnings. If it fails to push and you're using a self-hosted git service like Gitlab, you can turn off repository checks in the admin panel.
+- ``make test`` runs the basic test suite with ``pytest``
+- ``make cov`` runs the basic test suite with ``coverage``
+- ``make test-all`` runs the full test suite with ``tox``
+- ``make docs`` builds the HTML documentation
+Caution: zero-padded file modes
+-------------------------------
-cloning
--------
-The zero-padded file modes files above can cause issues while cloning, too. If you have
+This repository contains several zero-padded file modes that may cause issues
+when pushing this repository to git hosts other than GitHub. Fixing this is
+destructive to the commit history, so we suggest ignoring these warnings. If it
+fails to push and you're using a self-hosted git service like GitLab, you can
+turn off repository checks in the admin panel.
-::
+These files can also cause issues while cloning. If you have ::
[fetch]
fsckobjects = true
-or
-
-::
+or ::
[receive]
fsckObjects = true
-
-set in your git configuration file, cloning this repository will fail. The only solution is to set both of the above settings to false while cloning, and then setting them back to true after the cloning is finished.
+set in your git configuration file, cloning this repository will fail. The only
+solution is to set both of the above settings to false while cloning, and then
+setting them back to true after the cloning is finished.
diff --git a/MANIFEST.in b/MANIFEST.in
index f8d9c2ae..3616212e 100644
--- a/MANIFEST.in
+++ b/MANIFEST.in
@@ -1,4 +1,4 @@
-include Makefile CHANGES LICENSE AUTHORS
+include Makefile CHANGES LICENSE AUTHORS tox.ini
graft artwork
graft tests
diff --git a/Makefile b/Makefile
index 9bcdebc2..aef8a782 100644
--- a/Makefile
+++ b/Makefile
@@ -1,23 +1,35 @@
-.PHONY: clean-pyc ext-test test tox-test test-with-mem upload-docs docs audit
+.PHONY: all install-dev test coverage cov test-all tox docs audit release clean-pyc upload-docs ebook
-all: clean-pyc test
+all: test
-test:
- pip install -r test-requirements.txt -q
- FLASK_DEBUG= py.test tests examples
+install-dev:
+ pip install -q -e .[dev]
-tox-test:
+test: clean-pyc install-dev
+ pytest
+
+coverage: clean-pyc install-dev
+ pip install -q -e .[test]
+ coverage run -m pytest
+ coverage report
+ coverage html
+
+cov: coverage
+
+test-all: install-dev
tox
+tox: test-all
+
+docs: clean-pyc install-dev
+ $(MAKE) -C docs html
+
audit:
python setup.py audit
release:
python scripts/make-release.py
-ext-test:
- python tests/flaskext_test.py --browse
-
clean-pyc:
find . -name '*.pyc' -exec rm -f {} +
find . -name '*.pyo' -exec rm -f {} +
@@ -39,6 +51,3 @@ ebook:
@echo 'Requires X-forwarding for Qt features used in conversion (ssh -X).'
@echo 'Do not mind "Invalid value for ..." CSS errors if .mobi renders.'
ssh -X pocoo.org ebook-convert /var/www/flask.pocoo.org/docs/flask-docs.epub /var/www/flask.pocoo.org/docs/flask-docs.mobi --cover http://flask.pocoo.org/docs/_images/logo-full.png --authors 'Armin Ronacher'
-
-docs:
- $(MAKE) -C docs html
diff --git a/README b/README
index baea6b24..75c5e7b1 100644
--- a/README
+++ b/README
@@ -33,9 +33,9 @@
Good that you're asking. The tests are in the
tests/ folder. To run the tests use the
- `py.test` testing tool:
+ `pytest` testing tool:
- $ py.test
+ $ pytest
Details on contributing can be found in CONTRIBUTING.rst
diff --git a/docs/_static/debugger.png b/docs/_static/debugger.png
index 4f47229d..7d4181f6 100644
Binary files a/docs/_static/debugger.png and b/docs/_static/debugger.png differ
diff --git a/docs/_static/flask.png b/docs/_static/flask.png
index 5c603cc2..55cb8478 100644
Binary files a/docs/_static/flask.png and b/docs/_static/flask.png differ
diff --git a/docs/_static/flaskr.png b/docs/_static/flaskr.png
index 07d027dd..838f7604 100644
Binary files a/docs/_static/flaskr.png and b/docs/_static/flaskr.png differ
diff --git a/docs/_static/logo-full.png b/docs/_static/logo-full.png
index 5deaf1b8..ce236061 100644
Binary files a/docs/_static/logo-full.png and b/docs/_static/logo-full.png differ
diff --git a/docs/_static/no.png b/docs/_static/no.png
index 4ac1083d..644c3f70 100644
Binary files a/docs/_static/no.png and b/docs/_static/no.png differ
diff --git a/docs/_static/pycharm-runconfig.png b/docs/_static/pycharm-runconfig.png
new file mode 100644
index 00000000..dff21fa0
Binary files /dev/null and b/docs/_static/pycharm-runconfig.png differ
diff --git a/docs/_static/touch-icon.png b/docs/_static/touch-icon.png
index cd1e91e1..ef151f15 100644
Binary files a/docs/_static/touch-icon.png and b/docs/_static/touch-icon.png differ
diff --git a/docs/_static/yes.png b/docs/_static/yes.png
index ac27c4e1..56917ab2 100644
Binary files a/docs/_static/yes.png and b/docs/_static/yes.png differ
diff --git a/docs/_templates/sidebarintro.html b/docs/_templates/sidebarintro.html
index ec1608fd..c3cb2881 100644
--- a/docs/_templates/sidebarintro.html
+++ b/docs/_templates/sidebarintro.html
@@ -1,6 +1,6 @@
About Flask
- Flask is a micro webdevelopment framework for Python. You are currently
+ Flask is a micro web development framework for Python. You are currently
looking at the documentation of the development version.
diff --git a/docs/_themes b/docs/_themes
deleted file mode 160000
index 3d964b66..00000000
--- a/docs/_themes
+++ /dev/null
@@ -1 +0,0 @@
-Subproject commit 3d964b660442e23faedf801caed6e3c7bd42d5c9
diff --git a/docs/advanced_foreword.rst b/docs/advanced_foreword.rst
index 82b3dc58..bd56f53c 100644
--- a/docs/advanced_foreword.rst
+++ b/docs/advanced_foreword.rst
@@ -45,11 +45,3 @@ spam, links to malicious software, and the like.
Flask is no different from any other framework in that you the developer must
build with caution, watching for exploits when building to your requirements.
-
-Python 3 Support in Flask
--------------------------
-
-Flask, its dependencies, and most Flask extensions all support Python 3.
-If you want to use Flask with Python 3 have a look at the :ref:`python3-support` page.
-
-Continue to :ref:`installation` or the :ref:`quickstart`.
diff --git a/docs/api.rst b/docs/api.rst
index d77da3de..e24160c4 100644
--- a/docs/api.rst
+++ b/docs/api.rst
@@ -30,61 +30,12 @@ Incoming Request Data
.. autoclass:: Request
:members:
-
- .. attribute:: form
-
- A :class:`~werkzeug.datastructures.MultiDict` with the parsed form data from ``POST``
- or ``PUT`` requests. Please keep in mind that file uploads will not
- end up here, but instead in the :attr:`files` attribute.
-
- .. attribute:: args
-
- A :class:`~werkzeug.datastructures.MultiDict` with the parsed contents of the query
- string. (The part in the URL after the question mark).
-
- .. attribute:: values
-
- A :class:`~werkzeug.datastructures.CombinedMultiDict` with the contents of both
- :attr:`form` and :attr:`args`.
-
- .. attribute:: cookies
-
- A :class:`dict` with the contents of all cookies transmitted with
- the request.
-
- .. attribute:: stream
-
- If the incoming form data was not encoded with a known mimetype
- the data is stored unmodified in this stream for consumption. Most
- of the time it is a better idea to use :attr:`data` which will give
- you that data as a string. The stream only returns the data once.
-
- .. attribute:: headers
-
- The incoming request headers as a dictionary like object.
-
- .. attribute:: data
-
- Contains the incoming request data as string in case it came with
- a mimetype Flask does not handle.
-
- .. attribute:: files
-
- A :class:`~werkzeug.datastructures.MultiDict` with files uploaded as part of a
- ``POST`` or ``PUT`` request. Each file is stored as
- :class:`~werkzeug.datastructures.FileStorage` object. It basically behaves like a
- standard file object you know from Python, with the difference that
- it also has a :meth:`~werkzeug.datastructures.FileStorage.save` function that can
- store the file on the filesystem.
+ :inherited-members:
.. attribute:: environ
The underlying WSGI environment.
- .. attribute:: method
-
- The current request method (``POST``, ``GET`` etc.)
-
.. attribute:: path
.. attribute:: full_path
.. attribute:: script_root
@@ -114,15 +65,8 @@ Incoming Request Data
`url_root` ``u'http://www.example.com/myapplication/'``
============= ======================================================
- .. attribute:: is_xhr
- ``True`` if the request was triggered via a JavaScript
- `XMLHttpRequest`. This only works with libraries that support the
- ``X-Requested-With`` header and set it to `XMLHttpRequest`.
- Libraries that do that are prototype, jQuery and Mochikit and
- probably some more.
-
-.. class:: request
+.. attribute:: request
To access incoming request data, you can use the global `request`
object. Flask parses incoming request data for you and gives you
@@ -141,7 +85,7 @@ Response Objects
----------------
.. autoclass:: flask.Response
- :members: set_cookie, data, mimetype
+ :members: set_cookie, data, mimetype, is_json, get_json
.. attribute:: headers
@@ -159,12 +103,12 @@ Response Objects
Sessions
--------
-If you have the :attr:`Flask.secret_key` set you can use sessions in Flask
-applications. A session basically makes it possible to remember
-information from one request to another. The way Flask does this is by
-using a signed cookie. So the user can look at the session contents, but
-not modify it unless they know the secret key, so make sure to set that
-to something complex and unguessable.
+If you have set :attr:`Flask.secret_key` (or configured it from
+:data:`SECRET_KEY`) you can use sessions in Flask applications. A session makes
+it possible to remember information from one request to another. The way Flask
+does this is by using a signed cookie. The user can look at the session
+contents, but can't modify it unless they know the secret key, so make sure to
+set that to something complex and unguessable.
To access the current session you can use the :class:`session` object:
@@ -227,18 +171,6 @@ implementation that Flask is using.
.. autoclass:: SessionMixin
:members:
-.. autodata:: session_json_serializer
-
- This object provides dumping and loading methods similar to simplejson
- but it also tags certain builtin Python objects that commonly appear in
- sessions. Currently the following extended values are supported in
- the JSON it dumps:
-
- - :class:`~markupsafe.Markup` objects
- - :class:`~uuid.UUID` objects
- - :class:`~datetime.datetime` objects
- - :class:`tuple`\s
-
.. admonition:: Notice
The ``PERMANENT_SESSION_LIFETIME`` config key can also be an integer
@@ -410,6 +342,8 @@ you are using Flask 0.10 which implies that:
.. autoclass:: JSONDecoder
:members:
+.. automodule:: flask.json.tag
+
Template Rendering
------------------
@@ -705,6 +639,7 @@ The following signals exist in Flask:
.. _blinker: https://pypi.python.org/pypi/blinker
+.. _class-based-views:
Class-Based Views
-----------------
@@ -879,6 +814,8 @@ Command Line Interface
.. autoclass:: ScriptInfo
:members:
+.. autofunction:: load_dotenv
+
.. autofunction:: with_appcontext
.. autofunction:: pass_script_info
diff --git a/docs/appcontext.rst b/docs/appcontext.rst
index 166c5aa3..976609b6 100644
--- a/docs/appcontext.rst
+++ b/docs/appcontext.rst
@@ -5,31 +5,37 @@ The Application Context
.. versionadded:: 0.9
-One of the design ideas behind Flask is that there are two different
-“states” in which code is executed. The application setup state in which
-the application implicitly is on the module level. It starts when the
-:class:`Flask` object is instantiated, and it implicitly ends when the
-first request comes in. While the application is in this state a few
-assumptions are true:
-
-- the programmer can modify the application object safely.
-- no request handling happened so far
-- you have to have a reference to the application object in order to
- modify it, there is no magic proxy that can give you a reference to
- the application object you're currently creating or modifying.
-
-In contrast, during request handling, a couple of other rules exist:
-
-- while a request is active, the context local objects
- (:data:`flask.request` and others) point to the current request.
-- any code can get hold of these objects at any time.
-
-There is a third state which is sitting in between a little bit.
-Sometimes you are dealing with an application in a way that is similar to
-how you interact with applications during request handling; just that there
-is no request active. Consider, for instance, that you're sitting in an
-interactive Python shell and interacting with the application, or a
-command line application.
+One of the design ideas behind Flask is that there are at least two
+different “states” in which code is executed:
+
+1. The application setup state, in which the application implicitly is
+on the module level.
+
+ This state starts when the :class:`Flask` object is instantiated, and
+ it implicitly ends when the first request comes in. While the
+ application is in this state, a few assumptions are true:
+
+ - the programmer can modify the application object safely.
+ - no request handling happened so far
+ - you have to have a reference to the application object in order to
+ modify it, there is no magic proxy that can give you a reference to
+ the application object you're currently creating or modifying.
+
+2. In contrast, in the request handling state, a couple of other rules
+exist:
+
+ - while a request is active, the context local objects
+ (:data:`flask.request` and others) point to the current request.
+ - any code can get hold of these objects at any time.
+
+3. There is also a third state somewhere in between 'module-level' and
+'request-handling':
+
+ Sometimes you are dealing with an application in a way that is similar to
+ how you interact with applications during request handling, but without
+ there being an active request. Consider, for instance, that you're
+ sitting in an interactive Python shell and interacting with the
+ application, or a command line application.
The application context is what powers the :data:`~flask.current_app`
context local.
diff --git a/docs/blueprints.rst b/docs/blueprints.rst
index 89d3701e..98a3d630 100644
--- a/docs/blueprints.rst
+++ b/docs/blueprints.rst
@@ -177,11 +177,11 @@ the `template_folder` parameter to the :class:`Blueprint` constructor::
admin = Blueprint('admin', __name__, template_folder='templates')
For static files, the path can be absolute or relative to the blueprint
-resource folder.
+resource folder.
-The template folder is added to the search path of templates but with a lower
-priority than the actual application's template folder. That way you can
-easily override templates that a blueprint provides in the actual application.
+The template folder is added to the search path of templates but with a lower
+priority than the actual application's template folder. That way you can
+easily override templates that a blueprint provides in the actual application.
This also means that if you don't want a blueprint template to be accidentally
overridden, make sure that no other blueprint or actual application template
has the same relative path. When multiple blueprints provide the same relative
@@ -194,7 +194,7 @@ want to render the template ``'admin/index.html'`` and you have provided
this: :file:`yourapplication/admin/templates/admin/index.html`. The reason
for the extra ``admin`` folder is to avoid getting our template overridden
by a template named ``index.html`` in the actual application template
-folder.
+folder.
To further reiterate this: if you have a blueprint named ``admin`` and you
want to render a template called :file:`index.html` which is specific to this
@@ -245,4 +245,22 @@ Here is an example for a "404 Page Not Found" exception::
def page_not_found(e):
return render_template('pages/404.html')
+Most 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 errorhandler 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::
+
+ @app.errorhandler(404)
+ @app.errorhandler(405)
+ def _handle_api_error(ex):
+ if request.path.startswith('/api/'):
+ return jsonify_error(ex)
+ else:
+ return ex
+
More information on error handling see :ref:`errorpages`.
diff --git a/docs/changelog.rst b/docs/changelog.rst
index d6c5f48c..d9e113ec 100644
--- a/docs/changelog.rst
+++ b/docs/changelog.rst
@@ -1 +1 @@
-.. include:: ../CHANGES
+.. include:: ../CHANGES.rst
diff --git a/docs/cli.rst b/docs/cli.rst
index 7ddf50f3..456fdc03 100644
--- a/docs/cli.rst
+++ b/docs/cli.rst
@@ -1,89 +1,216 @@
+.. currentmodule:: flask
+
.. _cli:
Command Line Interface
======================
-.. versionadded:: 0.11
+Installing Flask installs the ``flask`` script, a `Click`_ command line
+interface, in your virtualenv. Executed from the terminal, this script gives
+access to built-in, extension, and application-defined commands. The ``--help``
+option will give more information about any commands and options.
-.. currentmodule:: flask
+.. _Click: http://click.pocoo.org/
-One of the nice new features in Flask 0.11 is the built-in integration of
-the `click `_ command line interface. This
-enables a wide range of new features for the Flask ecosystem and your own
-applications.
-Basic Usage
------------
+Application Discovery
+---------------------
-After installation of Flask you will now find a :command:`flask` script
-installed into your virtualenv. If you don't want to install Flask or you
-have a special use-case you can also use ``python -m flask`` to accomplish
-exactly the same.
+The ``flask`` command is installed by Flask, not your application; it must be
+told where to find your application in order to use it. The ``FLASK_APP``
+environment variable is used to specify how to load the application.
-The way this script works is by providing access to all the commands on
-your Flask application's :attr:`Flask.cli` instance as well as some
-built-in commands that are always there. Flask extensions can also
-register more commands there if they desire so.
+Unix Bash (Linux, Mac, etc.)::
-For the :command:`flask` script to work, an application needs to be
-discovered. This is achieved by exporting the ``FLASK_APP`` environment
-variable. It can be either set to an import path or to a filename of a
-Python module that contains a Flask application.
+ $ export FLASK_APP=hello
+ $ flask run
-In that imported file the name of the app needs to be called ``app`` or
-optionally be specified after a colon. For instance
-``mymodule:application`` would tell it to use the `application` object in
-the :file:`mymodule.py` file.
+Windows CMD::
-Given a :file:`hello.py` file with the application in it named ``app``
-this is how it can be run.
+ > set FLASK_APP=hello
+ > flask run
-Environment variables (On Windows use ``set`` instead of ``export``)::
+Windows PowerShell::
- export FLASK_APP=hello
- flask run
+ > $env:FLASK_APP = "hello"
+ > flask run
+
+While ``FLASK_APP`` supports a variety of options for specifying your
+application, most use cases should be simple. Here are the typical values:
+
+(nothing)
+ The file :file:`wsgi.py` is imported, automatically detecting an app
+ (``app``). This provides an easy way to create an app from a factory with
+ extra arguments.
+
+``FLASK_APP=hello``
+ The name is imported, automatically detecting an app (``app``) or factory
+ (``create_app``).
+
+----
+
+``FLASK_APP`` has three parts: an optional path that sets the current working
+directory, a Python file or dotted import path, and an optional variable
+name of the instance or factory. If the name is a factory, it can optionally
+be followed by arguments in parentheses. The following values demonstrate these
+parts:
+
+``FLASK_APP=src/hello``
+ Sets the current working directory to ``src`` then imports ``hello``.
+
+``FLASK_APP=hello.web``
+ Imports the path ``hello.web``.
+
+``FLASK_APP=hello:app2``
+ Uses the ``app2`` Flask instance in ``hello``.
+
+``FLASK_APP="hello:create_app('dev')"``
+ The ``create_app`` factory in ``hello`` is called with the string ``'dev'``
+ as the argument.
+
+If ``FLASK_APP`` is not set, the command will look for a file called
+:file:`wsgi.py` or :file:`app.py` and try to detect an application instance or
+factory.
+
+Within the given import, the command looks for an application instance named
+``app`` or ``application``, then any application instance. If no instance is
+found, the command looks for a factory function named ``create_app`` or
+``make_app`` that returns an instance.
+
+When calling an application factory, if the factory takes an argument named
+``info``, then the :class:`~cli.ScriptInfo` instance is passed as a keyword
+argument. If parentheses follow the factory name, their contents are parsed
+as Python literals and passes as arguments to the function. This means that
+strings must still be in quotes.
+
+
+Run the Development Server
+--------------------------
+
+The :func:`run ` command will start the development server. It
+replaces the :meth:`Flask.run` method in most cases. ::
+
+ $ flask run
+ * Serving Flask app "hello"
+ * Running on http://127.0.0.1:5000/ (Press CTRL+C to quit)
+
+.. warning:: Do not use this command to run your application in production.
+ Only use the development server during development. The development server
+ is provided for convenience, but is not designed to be particularly secure,
+ stable, or efficient. See :ref:`deployment` for how to run in production.
+
+
+Open a Shell
+------------
+
+To explore the data in your application, you can start an interactive Python
+shell with the :func:`shell ` command. An application
+context will be active, and the app instance will be imported. ::
+
+ $ flask shell
+ Python 3.6.2 (default, Jul 20 2017, 03:52:27)
+ [GCC 7.1.1 20170630] on linux
+ App: example
+ Instance: /home/user/Projects/hello/instance
+ >>>
+
+Use :meth:`~Flask.shell_context_processor` to add other automatic imports.
-Or with a filename::
- export FLASK_APP=/path/to/hello.py
- flask run
+Environments
+------------
-Virtualenv Integration
-----------------------
+.. versionadded:: 1.0
-If you are constantly working with a virtualenv you can also put the
-``export FLASK_APP`` into your ``activate`` script by adding it to the
-bottom of the file. That way every time you activate your virtualenv you
-automatically also activate the correct application name.
+The environment in which the Flask app runs is set by the
+:envvar:`FLASK_ENV` environment variable. If not set it defaults to
+``production``. The other recognized environment is ``development``.
+Flask and extensions may choose to enable behaviors based on the
+environment.
-Debug Flag
+If the env is set to ``development``, the ``flask`` command will enable
+debug mode and ``flask run`` will enable the interactive debugger and
+reloader.
+
+::
+
+ $ FLASK_ENV=development flask run
+ * Serving Flask app "hello"
+ * Environment: development
+ * Debug mode: on
+ * Running on http://127.0.0.1:5000/ (Press CTRL+C to quit)
+ * Restarting with inotify reloader
+ * Debugger is active!
+ * Debugger PIN: 223-456-919
+
+
+Debug Mode
----------
-The :command:`flask` script can also be instructed to enable the debug
-mode of the application automatically by exporting ``FLASK_DEBUG``. If
-set to ``1`` debug is enabled or ``0`` disables it::
+Debug mode will be enabled when :envvar:`FLASK_ENV` is ``development``,
+as described above. If you want to control debug mode separately, use
+:envvar:`FLASK_DEBUG`. The value ``1`` enables it, ``0`` disables it.
- export FLASK_DEBUG=1
-Running a Shell
----------------
+.. _dotenv:
+
+Environment Variables From dotenv
+---------------------------------
+
+Rather than setting ``FLASK_APP`` each time you open a new terminal, you can
+use Flask's dotenv support to set environment variables automatically.
+
+If `python-dotenv`_ is installed, running the ``flask`` command will set
+environment variables defined in the files :file:`.env` and :file:`.flaskenv`.
+This can be used to avoid having to set ``FLASK_APP`` manually every time you
+open a new terminal, and to set configuration using environment variables
+similar to how some deployment services work.
+
+Variables set on the command line are used over those set in :file:`.env`,
+which are used over those set in :file:`.flaskenv`. :file:`.flaskenv` should be
+used for public variables, such as ``FLASK_APP``, while :file:`.env` should not
+be committed to your repository so that it can set private variables.
+
+Directories are scanned upwards from the directory you call ``flask``
+from to locate the files. The current working directory will be set to the
+location of the file, with the assumption that that is the top level project
+directory.
+
+The files are only loaded by the ``flask`` command or calling
+:meth:`~Flask.run`. If you would like to load these files when running in
+production, you should call :func:`~cli.load_dotenv` manually.
+
+.. _python-dotenv: https://github.com/theskumar/python-dotenv#readme
+
-To run an interactive Python shell you can use the ``shell`` command::
+Environment Variables From virtualenv
+-------------------------------------
- flask shell
+If you do not want to install dotenv support, you can still set environment
+variables by adding them to the end of the virtualenv's :file:`activate`
+script. Activating the virtualenv will set the variables.
+
+Unix Bash, :file:`venv/bin/activate`::
+
+ export FLASK_APP=hello
+
+Windows CMD, :file:`venv\\Scripts\\activate.bat`::
+
+ set FLASK_APP=hello
+
+It is preferred to use dotenv support over this, since :file:`.flaskenv` can be
+committed to the repository so that it works automatically wherever the project
+is checked out.
-This will start up an interactive Python shell, setup the correct
-application context and setup the local variables in the shell. This is
-done by invoking the :meth:`Flask.make_shell_context` method of the
-application. By default you have access to your ``app`` and :data:`g`.
Custom Commands
---------------
-If you want to add more commands to the shell script you can do this
-easily. Flask uses `click`_ for the command interface which makes
-creating custom commands very easy. For instance if you want a shell
-command to initialize the database you can do this::
+The ``flask`` command is implemented using `Click`_. See that project's
+documentation for full information about writing commands.
+
+This example adds the command ``create_user`` that takes the argument
+``name``. ::
import click
from flask import Flask
@@ -91,158 +218,207 @@ command to initialize the database you can do this::
app = Flask(__name__)
@app.cli.command()
- def initdb():
- """Initialize the database."""
- click.echo('Init the db')
+ @click.argument('name')
+ def create_user(name):
+ ...
+
+::
+
+ flask create_user admin
+
+This example adds the same command, but as ``user create``, a command in a
+group. This is useful if you want to organize multiple related commands. ::
+
+ import click
+ from flask import Flask
+ from flask.cli import AppGroup
+
+ app = Flask(__name__)
+ user_cli = AppGroup('user')
+
+ @user_cli.command('create')
+ @click.argument('name')
+ def create_user(name):
+ ...
+
+ app.cli.add_command(user_cli)
+
+::
-The command will then show up on the command line::
+ flask user create demo
+
+See :ref:`testing-cli` for an overview of how to test your custom
+commands.
- $ flask initdb
- Init the db
Application Context
--------------------
+~~~~~~~~~~~~~~~~~~~
+
+Commands added using the Flask app's :attr:`~Flask.cli`
+:meth:`~cli.AppGroup.command` decorator will be executed with an application
+context pushed, so your command and extensions have access to the app and its
+configuration. If you create a command using the Click :func:`~click.command`
+decorator instead of the Flask decorator, you can use
+:func:`~cli.with_appcontext` to get the same behavior. ::
+
+ import click
+ from flask.cli import with_appcontext
+
+ @click.command
+ @with_appcontext
+ def do_work():
+ ...
-Most commands operate on the application so it makes a lot of sense if
-they have the application context setup. Because of this, if you register
-a callback on ``app.cli`` with the :meth:`~flask.cli.AppGroup.command` the
-callback will automatically be wrapped through :func:`cli.with_appcontext`
-which informs the cli system to ensure that an application context is set
-up. This behavior is not available if a command is added later with
-:func:`~click.Group.add_command` or through other means.
+ app.cli.add_command(do_work)
-It can also be disabled by passing ``with_appcontext=False`` to the
-decorator::
+If you're sure a command doesn't need the context, you can disable it::
@app.cli.command(with_appcontext=False)
- def example():
- pass
+ def do_work():
+ ...
-Factory Functions
------------------
-In case you are using factory functions to create your application (see
-:ref:`app-factories`) you will discover that the :command:`flask` command
-cannot work with them directly. Flask won't be able to figure out how to
-instantiate your application properly by itself. Because of this reason
-the recommendation is to create a separate file that instantiates
-applications. This is not the only way to make this work. Another is the
-:ref:`custom-scripts` support.
+Plugins
+-------
-For instance if you have a factory function that creates an application
-from a filename you could make a separate file that creates such an
-application from an environment variable.
+Flask will automatically load commands specified in the ``flask.commands``
+`entry point`_. This is useful for extensions that want to add commands when
+they are installed. Entry points are specified in :file:`setup.py` ::
+
+ from setuptools import setup
-This could be a file named :file:`autoapp.py` with these contents::
+ setup(
+ name='flask-my-extension',
+ ...,
+ entry_points={
+ 'flask.commands': [
+ 'my-command=flask_my_extension.commands:cli'
+ ],
+ },
+ )
- import os
- from yourapplication import create_app
- app = create_app(os.environ['YOURAPPLICATION_CONFIG'])
-Once this has happened you can make the flask command automatically pick
-it up::
+.. _entry point: https://packaging.python.org/tutorials/distributing-packages/#entry-points
+
+Inside :file:`flask_my_extension/commands.py` you can then export a Click
+object::
+
+ import click
+
+ @click.command()
+ def cli():
+ ...
- export YOURAPPLICATION_CONFIG=/path/to/config.cfg
- export FLASK_APP=/path/to/autoapp.py
+Once that package is installed in the same virtualenv as your Flask project,
+you can run ``flask my-command`` to invoke the command.
-From this point onwards :command:`flask` will find your application.
.. _custom-scripts:
Custom Scripts
--------------
-While the most common way is to use the :command:`flask` command, you can
-also make your own "driver scripts". Since Flask uses click for the
-scripts there is no reason you cannot hook these scripts into any click
-application. There is one big caveat and that is, that commands
-registered to :attr:`Flask.cli` will expect to be (indirectly at least)
-launched from a :class:`flask.cli.FlaskGroup` click group. This is
-necessary so that the commands know which Flask application they have to
-work with.
-
-To understand why you might want custom scripts you need to understand how
-click finds and executes the Flask application. If you use the
-:command:`flask` script you specify the application to work with on the
-command line or environment variable as an import name. This is simple
-but it has some limitations. Primarily it does not work with application
-factory functions (see :ref:`app-factories`).
-
-With a custom script you don't have this problem as you can fully
-customize how the application will be created. This is very useful if you
-write reusable applications that you want to ship to users and they should
-be presented with a custom management script.
-
-To explain all of this, here is an example :file:`manage.py` script that
-manages a hypothetical wiki application. We will go through the details
-afterwards::
-
- import os
+When you are using the app factory pattern, it may be more convenient to define
+your own Click script. Instead of using ``FLASK_APP`` and letting Flask load
+your application, you can create your own Click object and export it as a
+`console script`_ entry point.
+
+Create an instance of :class:`~cli.FlaskGroup` and pass it the factory::
+
import click
+ from flask import Flask
from flask.cli import FlaskGroup
- def create_wiki_app(info):
- from yourwiki import create_app
- return create_app(
- config=os.environ.get('WIKI_CONFIG', 'wikiconfig.py'))
+ def create_app():
+ app = Flask('wiki')
+ # other setup
+ return app
- @click.group(cls=FlaskGroup, create_app=create_wiki_app)
+ @click.group(cls=FlaskGroup, create_app=create_app)
def cli():
- """This is a management script for the wiki application."""
-
- if __name__ == '__main__':
- cli()
-
-That's a lot of code for not much, so let's go through all parts step by
-step.
-
-1. First we import the ``click`` library as well as the click extensions
- from the ``flask.cli`` package. Primarily we are here interested
- in the :class:`~flask.cli.FlaskGroup` click group.
-2. The next thing we do is defining a function that is invoked with the
- script info object (:class:`~flask.cli.ScriptInfo`) from Flask and its
- purpose is to fully import and create the application. This can
- either directly import an application object or create it (see
- :ref:`app-factories`). In this case we load the config from an
- environment variable.
-3. Next step is to create a :class:`FlaskGroup`. In this case we just
- make an empty function with a help doc string that just does nothing
- and then pass the ``create_wiki_app`` function as a factory function.
-
- Whenever click now needs to operate on a Flask application it will
- call that function with the script info and ask for it to be created.
-4. All is rounded up by invoking the script.
-
-CLI Plugins
------------
-
-Flask extensions can always patch the :attr:`Flask.cli` instance with more
-commands if they want. However there is a second way to add CLI plugins
-to Flask which is through ``setuptools``. If you make a Python package that
-should export a Flask command line plugin you can ship a :file:`setup.py` file
-that declares an entrypoint that points to a click command:
-
-Example :file:`setup.py`::
+ """Management script for the Wiki application."""
+
+Define the entry point in :file:`setup.py`::
from setuptools import setup
setup(
name='flask-my-extension',
- ...
- entry_points='''
- [flask.commands]
- my-command=mypackage.commands:cli
- ''',
+ ...,
+ entry_points={
+ 'console_scripts': [
+ 'wiki=wiki:cli'
+ ],
+ },
)
-Inside :file:`mypackage/commands.py` you can then export a Click object::
+Install the application in the virtualenv in editable mode and the custom
+script is available. Note that you don't need to set ``FLASK_APP``. ::
- import click
+ $ pip install -e .
+ $ wiki run
- @click.command()
- def cli():
- """This is an example command."""
+.. admonition:: Errors in Custom Scripts
+
+ When using a custom script, if you introduce an error in your
+ module-level code, the reloader will fail because it can no longer
+ load the entry point.
+
+ The ``flask`` command, being separate from your code, does not have
+ this issue and is recommended in most cases.
+
+.. _console script: https://packaging.python.org/tutorials/distributing-packages/#console-scripts
+
+
+PyCharm Integration
+-------------------
+
+Prior to PyCharm 2018.1, the Flask CLI features weren't yet fully
+integrated into PyCharm. We have to do a few tweaks to get them working
+smoothly. These instructions should be similar for any other IDE you
+might want to use.
+
+In PyCharm, with your project open, click on *Run* from the menu bar and
+go to *Edit Configurations*. You'll be greeted by a screen similar to
+this:
+
+.. image:: _static/pycharm-runconfig.png
+ :align: center
+ :class: screenshot
+ :alt: screenshot of pycharm's run configuration settings
+
+There's quite a few options to change, but once we've done it for one
+command, we can easily copy the entire configuration and make a single
+tweak to give us access to other commands, including any custom ones you
+may implement yourself.
+
+Click the + (*Add New Configuration*) button and select *Python*. Give
+the configuration a good descriptive name such as "Run Flask Server".
+For the ``flask run`` command, check "Single instance only" since you
+can't run the server more than once at the same time.
+
+Select *Module name* from the dropdown (**A**) then input ``flask``.
+
+The *Parameters* field (**B**) is set to the CLI command to execute
+(with any arguments). In this example we use ``run``, which will run
+the development server.
+
+You can skip this next step if you're using :ref:`dotenv`. We need to
+add an environment variable (**C**) to identify our application. Click
+on the browse button and add an entry with ``FLASK_APP`` on the left and
+the Python import or file on the right (``hello`` for example).
+
+Next we need to set the working directory (**D**) to be the folder where
+our application resides.
+
+If you have installed your project as a package in your virtualenv, you
+may untick the *PYTHONPATH* options (**E**). This will more accurately
+match how you deploy the app later.
+
+Click *Apply* to save the configuration, or *OK* to save and close the
+window. Select the configuration in the main PyCharm window and click
+the play button next to it to run the server.
-Once that package is installed in the same virtualenv as Flask itself you
-can run ``flask my-command`` to invoke your command. This is useful to
-provide extra functionality that Flask itself cannot ship.
+Now that we have a configuration which runs ``flask run`` from within
+PyCharm, we can copy that configuration and alter the *Script* argument
+to run a different CLI command, e.g. ``flask shell``.
diff --git a/docs/conf.py b/docs/conf.py
index b37427a8..94cae16d 100644
--- a/docs/conf.py
+++ b/docs/conf.py
@@ -11,15 +11,17 @@
# All configuration values have a default; values that are commented out
# serve to show the default.
from __future__ import print_function
-from datetime import datetime
import os
import sys
import pkg_resources
+import time
+import datetime
+
+BUILD_DATE = datetime.datetime.utcfromtimestamp(int(os.environ.get('SOURCE_DATE_EPOCH', time.time())))
# If extensions (or modules to document with autodoc) are in another directory,
# add these directories to sys.path here. If the directory is relative to the
# documentation root, use os.path.abspath to make it absolute, like shown here.
-sys.path.append(os.path.join(os.path.dirname(__file__), '_themes'))
sys.path.append(os.path.dirname(__file__))
# -- General configuration -----------------------------------------------------
@@ -35,6 +37,14 @@ extensions = [
'flaskdocext'
]
+try:
+ __import__('sphinxcontrib.log_cabinet')
+except ImportError:
+ print('sphinxcontrib-log-cabinet is not installed.')
+ print('Changelog directives will not be re-organized.')
+else:
+ extensions.append('sphinxcontrib.log_cabinet')
+
# Add any paths that contain templates here, relative to this directory.
templates_path = ['_templates']
@@ -49,7 +59,7 @@ master_doc = 'index'
# General information about the project.
project = u'Flask'
-copyright = u'2010 - {0}, Armin Ronacher'.format(datetime.utcnow().year)
+copyright = u'2010 - {0}, Armin Ronacher'.format(BUILD_DATE.year)
# The version info for the project you're documenting, acts as replacement for
# |version| and |release|, also used in various other places throughout the
@@ -110,7 +120,7 @@ exclude_patterns = ['_build']
# html_theme_options = {}
# Add any paths that contain custom themes here, relative to this directory.
-html_theme_path = ['_themes']
+# html_theme_path = ['_themes']
# The name for this set of Sphinx documents. If None, it defaults to
# " v documentation".
@@ -231,7 +241,7 @@ latex_additional_files = ['flaskstyle.sty', 'logo.pdf']
# The scheme of the identifier. Typical schemes are ISBN or URL.
#epub_scheme = ''
-# The unique identifier of the text. This can be a ISBN number
+# The unique identifier of the text. This can be an ISBN number
# or the project homepage.
#epub_identifier = ''
@@ -257,26 +267,15 @@ intersphinx_mapping = {
'werkzeug': ('http://werkzeug.pocoo.org/docs/', None),
'click': ('http://click.pocoo.org/', None),
'jinja': ('http://jinja.pocoo.org/docs/', None),
- 'sqlalchemy': ('http://docs.sqlalchemy.org/en/latest/', None),
+ 'itsdangerous': ('https://pythonhosted.org/itsdangerous', None),
+ 'sqlalchemy': ('https://docs.sqlalchemy.org/en/latest/', None),
'wtforms': ('https://wtforms.readthedocs.io/en/latest/', None),
- 'blinker': ('https://pythonhosted.org/blinker/', None)
+ 'blinker': ('https://pythonhosted.org/blinker/', None),
}
-try:
- __import__('flask_theme_support')
- pygments_style = 'flask_theme_support.FlaskyStyle'
- html_theme = 'flask'
- html_theme_options = {
- 'touch_icon': 'touch-icon.png'
- }
-except ImportError:
- print('-' * 74)
- print('Warning: Flask themes unavailable. Building with default theme')
- print('If you want the Flask themes, run this command and build again:')
- print()
- print(' git submodule update --init')
- print('-' * 74)
-
+html_theme_options = {
+ 'touch_icon': 'touch-icon.png'
+}
# unwrap decorators
def unwrap_decorators():
diff --git a/docs/config.rst b/docs/config.rst
index 89fa0924..2e2833f9 100644
--- a/docs/config.rst
+++ b/docs/config.rst
@@ -3,8 +3,6 @@
Configuration Handling
======================
-.. versionadded:: 0.3
-
Applications need some kind of configuration. There are different settings
you might want to change depending on the application environment like
toggling the debug mode, setting the secret key, and other such
@@ -22,6 +20,7 @@ object. This is the place where Flask itself puts certain configuration
values and also where extensions can put their configuration values. But
this is also where you can have your own configuration.
+
Configuration Basics
--------------------
@@ -29,193 +28,319 @@ The :attr:`~flask.Flask.config` is actually a subclass of a dictionary and
can be modified just like any dictionary::
app = Flask(__name__)
- app.config['DEBUG'] = True
+ app.config['TESTING'] = True
Certain configuration values are also forwarded to the
:attr:`~flask.Flask` object so you can read and write them from there::
- app.debug = True
+ app.testing = True
To update multiple keys at once you can use the :meth:`dict.update`
method::
app.config.update(
- DEBUG=True,
- SECRET_KEY='...'
+ TESTING=True,
+ SECRET_KEY=b'_5#y2L"F4Q8z\n\xec]/'
)
+
+Environment and Debug Features
+------------------------------
+
+The :data:`ENV` and :data:`DEBUG` config values are special because they
+may behave inconsistently if changed after the app has begun setting up.
+In order to set the environment and debug mode reliably, Flask uses
+environment variables.
+
+The environment is used to indicate to Flask, extensions, and other
+programs, like Sentry, what context Flask is running in. It is
+controlled with the :envvar:`FLASK_ENV` environment variable and
+defaults to ``production``.
+
+Setting :envvar:`FLASK_ENV` to ``development`` will enable debug mode.
+``flask run`` will use the interactive debugger and reloader by default
+in debug mode. To control this separately from the environment, use the
+:envvar:`FLASK_DEBUG` flag.
+
+.. versionchanged:: 1.0
+ Added :envvar:`FLASK_ENV` to control the environment separately
+ from debug mode. The development environment enables debug mode.
+
+To switch Flask to the development environment and enable debug mode,
+set :envvar:`FLASK_ENV`::
+
+ $ export FLASK_ENV=development
+ $ flask run
+
+(On Windows, use ``set`` instead of ``export``.)
+
+Using the environment variables as described above is recommended. While
+it is possible to set :data:`ENV` and :data:`DEBUG` in your config or
+code, this is strongly discouraged. They can't be read early by the
+``flask`` command, and some systems or extensions may have already
+configured themselves based on a previous value.
+
+
Builtin Configuration Values
----------------------------
The following configuration values are used internally by Flask:
-.. tabularcolumns:: |p{6.5cm}|p{8.5cm}|
-
-================================= =========================================
-``DEBUG`` enable/disable debug mode
-``TESTING`` enable/disable testing mode
-``PROPAGATE_EXCEPTIONS`` explicitly enable or disable the
- propagation of exceptions. If not set or
- explicitly set to ``None`` this is
- implicitly true if either ``TESTING`` or
- ``DEBUG`` is true.
-``PRESERVE_CONTEXT_ON_EXCEPTION`` By default if the application is in
- debug mode the request context is not
- popped on exceptions to enable debuggers
- to introspect the data. This can be
- disabled by this key. You can also use
- this setting to force-enable it for non
- debug execution which might be useful to
- debug production applications (but also
- very risky).
-``SECRET_KEY`` the secret key
-``SESSION_COOKIE_NAME`` the name of the session cookie
-``SESSION_COOKIE_DOMAIN`` the domain for the session cookie. If
- this is not set, the cookie will be
- valid for all subdomains of
- ``SERVER_NAME``.
-``SESSION_COOKIE_PATH`` the path for the session cookie. If
- this is not set the cookie will be valid
- for all of ``APPLICATION_ROOT`` or if
- that is not set for ``'/'``.
-``SESSION_COOKIE_HTTPONLY`` controls if the cookie should be set
- with the httponly flag. Defaults to
- ``True``.
-``SESSION_COOKIE_SECURE`` controls if the cookie should be set
- with the secure flag. Defaults to
- ``False``.
-``PERMANENT_SESSION_LIFETIME`` the lifetime of a permanent session as
- :class:`datetime.timedelta` object.
- Starting with Flask 0.8 this can also be
- an integer representing seconds.
-``SESSION_REFRESH_EACH_REQUEST`` this flag controls how permanent
- sessions are refreshed. If set to ``True``
- (which is the default) then the cookie
- is refreshed each request which
- automatically bumps the lifetime. If
- set to ``False`` a `set-cookie` header is
- only sent if the session is modified.
- Non permanent sessions are not affected
- by this.
-``USE_X_SENDFILE`` enable/disable x-sendfile
-``LOGGER_NAME`` the name of the logger
-``LOGGER_HANDLER_POLICY`` the policy of the default logging
- handler. The default is ``'always'``
- which means that the default logging
- handler is always active. ``'debug'``
- will only activate logging in debug
- mode, ``'production'`` will only log in
- production and ``'never'`` disables it
- entirely.
-``SERVER_NAME`` the name and port number of the server.
- Required for subdomain support (e.g.:
- ``'myapp.dev:5000'``) Note that
- localhost does not support subdomains so
- setting this to “localhost” does not
- help. Setting a ``SERVER_NAME`` also
- by default enables URL generation
- without a request context but with an
- application context.
-``APPLICATION_ROOT`` If the application does not occupy
- a whole domain or subdomain this can
- be set to the path where the application
- is configured to live. This is for
- session cookie as path value. If
- domains are used, this should be
- ``None``.
-``MAX_CONTENT_LENGTH`` If set to a value in bytes, Flask will
- reject incoming requests with a
- content length greater than this by
- returning a 413 status code.
-``SEND_FILE_MAX_AGE_DEFAULT`` Default cache control max age to use with
- :meth:`~flask.Flask.send_static_file` (the
- default static file handler) and
- :func:`~flask.send_file`, as
- :class:`datetime.timedelta` or as seconds.
- Override this value on a per-file
- basis using the
- :meth:`~flask.Flask.get_send_file_max_age`
- hook on :class:`~flask.Flask` or
- :class:`~flask.Blueprint`,
- respectively. Defaults to 43200 (12 hours).
-``TRAP_HTTP_EXCEPTIONS`` If this is set to ``True`` Flask will
- not execute the error handlers of HTTP
- exceptions but instead treat the
- exception like any other and bubble it
- through the exception stack. This is
- helpful for hairy debugging situations
- where you have to find out where an HTTP
- exception is coming from.
-``TRAP_BAD_REQUEST_ERRORS`` Werkzeug's internal data structures that
- deal with request specific data will
- raise special key errors that are also
- bad request exceptions. Likewise many
- operations can implicitly fail with a
- BadRequest exception for consistency.
- Since it's nice for debugging to know
- why exactly it failed this flag can be
- used to debug those situations. If this
- config is set to ``True`` you will get
- a regular traceback instead.
-``PREFERRED_URL_SCHEME`` The URL scheme that should be used for
- URL generation if no URL scheme is
- available. This defaults to ``http``.
-``JSON_AS_ASCII`` By default Flask serialize object to
- ascii-encoded JSON. If this is set to
- ``False`` Flask will not encode to ASCII
- and output strings as-is and return
- unicode strings. ``jsonify`` will
- automatically encode it in ``utf-8``
- then for transport for instance.
-``JSON_SORT_KEYS`` By default Flask will serialize JSON
- objects in a way that the keys are
- ordered. This is done in order to
- ensure that independent of the hash seed
- of the dictionary the return value will
- be consistent to not trash external HTTP
- caches. You can override the default
- behavior by changing this variable.
- This is not recommended but might give
- you a performance improvement on the
- cost of cacheability.
-``JSONIFY_PRETTYPRINT_REGULAR`` If this is set to ``True`` (the default)
- jsonify responses will be pretty printed
- if they are not requested by an
- XMLHttpRequest object (controlled by
- the ``X-Requested-With`` header)
-``JSONIFY_MIMETYPE`` MIME type used for jsonify responses.
-``TEMPLATES_AUTO_RELOAD`` Whether to check for modifications of
- the template source and reload it
- automatically. By default the value is
- ``None`` which means that Flask checks
- original file only in debug mode.
-``EXPLAIN_TEMPLATE_LOADING`` If this is enabled then every attempt to
- load a template will write an info
- message to the logger explaining the
- attempts to locate the template. This
- can be useful to figure out why
- templates cannot be found or wrong
- templates appear to be loaded.
-================================= =========================================
-
-.. admonition:: More on ``SERVER_NAME``
-
- The ``SERVER_NAME`` key is used for the subdomain support. Because
- Flask cannot guess the subdomain part without the knowledge of the
- actual server name, this is required if you want to work with
- subdomains. This is also used for the session cookie.
-
- Please keep in mind that not only Flask has the problem of not knowing
- what subdomains are, your web browser does as well. Most modern web
- browsers will not allow cross-subdomain cookies to be set on a
- server name without dots in it. So if your server name is
- ``'localhost'`` you will not be able to set a cookie for
- ``'localhost'`` and every subdomain of it. Please choose a different
- server name in that case, like ``'myapplication.local'`` and add
- this name + the subdomains you want to use into your host config
- or setup a local `bind`_.
-
-.. _bind: https://www.isc.org/downloads/bind/
+.. py:data:: ENV
+
+ What environment the app is running in. Flask and extensions may
+ enable behaviors based on the environment, such as enabling debug
+ mode. The :attr:`~flask.Flask.env` attribute maps to this config
+ key. This is set by the :envvar:`FLASK_ENV` environment variable and
+ may not behave as expected if set in code.
+
+ **Do not enable development when deploying in production.**
+
+ Default: ``'production'``
+
+ .. versionadded:: 1.0
+
+.. py:data:: DEBUG
+
+ Whether debug mode is enabled. When using ``flask run`` to start the
+ development server, an interactive debugger will be shown for
+ unhandled exceptions, and the server will be reloaded when code
+ changes. The :attr:`~flask.Flask.debug` attribute maps to this
+ config key. This is enabled when :data:`ENV` is ``'development'``
+ and is overridden by the ``FLASK_DEBUG`` environment variable. It
+ may not behave as expected if set in code.
+
+ **Do not enable debug mode when deploying in production.**
+
+ Default: ``True`` if :data:`ENV` is ``'production'``, or ``False``
+ otherwise.
+
+.. py:data:: TESTING
+
+ Enable testing mode. Exceptions are propagated rather than handled by the
+ the app's error handlers. Extensions may also change their behavior to
+ facilitate easier testing. You should enable this in your own tests.
+
+ Default: ``False``
+
+.. py:data:: PROPAGATE_EXCEPTIONS
+
+ Exceptions are re-raised rather than being handled by the app's error
+ handlers. If not set, this is implicitly true if ``TESTING`` or ``DEBUG``
+ is enabled.
+
+ Default: ``None``
+
+.. py:data:: PRESERVE_CONTEXT_ON_EXCEPTION
+
+ Don't pop the request context when an exception occurs. If not set, this
+ is true if ``DEBUG`` is true. This allows debuggers to introspect the
+ request data on errors, and should normally not need to be set directly.
+
+ Default: ``None``
+
+.. py:data:: TRAP_HTTP_EXCEPTIONS
+
+ If there is no handler for an ``HTTPException``-type exception, re-raise it
+ to be handled by the interactive debugger instead of returning it as a
+ simple error response.
+
+ Default: ``False``
+
+.. py:data:: TRAP_BAD_REQUEST_ERRORS
+
+ Trying to access a key that doesn't exist from request dicts like ``args``
+ and ``form`` will return a 400 Bad Request error page. Enable this to treat
+ the error as an unhandled exception instead so that you get the interactive
+ debugger. This is a more specific version of ``TRAP_HTTP_EXCEPTIONS``. If
+ unset, it is enabled in debug mode.
+
+ Default: ``None``
+
+.. py:data:: SECRET_KEY
+
+ A secret key that will be used for securely signing the session cookie
+ and can be used for any other security related needs by extensions or your
+ application. It should be a long random string of bytes, although unicode
+ is accepted too. For example, copy the output of this to your config::
+
+ python -c 'import os; print(os.urandom(16))'
+ b'_5#y2L"F4Q8z\n\xec]/'
+
+ **Do not reveal the secret key when posting questions or committing code.**
+
+ Default: ``None``
+
+.. py:data:: SESSION_COOKIE_NAME
+
+ The name of the session cookie. Can be changed in case you already have a
+ cookie with the same name.
+
+ Default: ``'session'``
+
+.. py:data:: SESSION_COOKIE_DOMAIN
+
+ The domain match rule that the session cookie will be valid for. If not
+ set, the cookie will be valid for all subdomains of ``SERVER_NAME``. If
+ ``False``, the cookie's domain will not be set.
+
+ Default: ``None``
+
+.. py:data:: SESSION_COOKIE_PATH
+
+ The path that the session cookie will be valid for. If not set, the cookie
+ will be valid underneath ``APPLICATION_ROOT`` or ``/`` if that is not set.
+
+ Default: ``None``
+
+.. py:data:: SESSION_COOKIE_HTTPONLY
+
+ Browsers will not allow JavaScript access to cookies marked as "HTTP only"
+ for security.
+
+ Default: ``True``
+
+.. py:data:: SESSION_COOKIE_SECURE
+
+ Browsers will only send cookies with requests over HTTPS if the cookie is
+ marked "secure". The application must be served over HTTPS for this to make
+ sense.
+
+ Default: ``False``
+
+.. py:data:: SESSION_COOKIE_SAMESITE
+
+ Restrict how cookies are sent with requests from external sites. Can
+ be set to ``'Lax'`` (recommended) or ``'Strict'``.
+ See :ref:`security-cookie`.
+
+ Default: ``None``
+
+ .. versionadded:: 1.0
+
+.. py:data:: PERMANENT_SESSION_LIFETIME
+
+ If ``session.permanent`` is true, the cookie's expiration will be set this
+ number of seconds in the future. Can either be a
+ :class:`datetime.timedelta` or an ``int``.
+
+ Flask's default cookie implementation validates that the cryptographic
+ signature is not older than this value.
+
+ Default: ``timedelta(days=31)`` (``2678400`` seconds)
+
+.. py:data:: SESSION_REFRESH_EACH_REQUEST
+
+ Control whether the cookie is sent with every response when
+ ``session.permanent`` is true. Sending the cookie every time (the default)
+ can more reliably keep the session from expiring, but uses more bandwidth.
+ Non-permanent sessions are not affected.
+
+ Default: ``True``
+
+.. py:data:: USE_X_SENDFILE
+
+ When serving files, set the ``X-Sendfile`` header instead of serving the
+ data with Flask. Some web servers, such as Apache, recognize this and serve
+ the data more efficiently. This only makes sense when using such a server.
+
+ Default: ``False``
+
+.. py:data:: SEND_FILE_MAX_AGE_DEFAULT
+
+ When serving files, set the cache control max age to this number of
+ seconds. Can either be a :class:`datetime.timedelta` or an ``int``.
+ Override this value on a per-file basis using
+ :meth:`~flask.Flask.get_send_file_max_age` on the application or blueprint.
+
+ Default: ``timedelta(hours=12)`` (``43200`` seconds)
+
+.. py:data:: SERVER_NAME
+
+ Inform the application what host and port it is bound to. Required for
+ subdomain route matching support.
+
+ If set, will be used for the session cookie domain if
+ ``SESSION_COOKIE_DOMAIN`` is not set. Modern web browsers will not allow
+ setting cookies for domains without a dot. To use a domain locally,
+ add any names that should route to the app to your ``hosts`` file. ::
+
+ 127.0.0.1 localhost.dev
+
+ If set, ``url_for`` can generate external URLs with only an application
+ context instead of a request context.
+
+ Default: ``None``
+
+.. py:data:: APPLICATION_ROOT
+
+ Inform the application what path it is mounted under by the application /
+ web server.
+
+ Will be used for the session cookie path if ``SESSION_COOKIE_PATH`` is not
+ set.
+
+ Default: ``'/'``
+
+.. py:data:: PREFERRED_URL_SCHEME
+
+ Use this scheme for generating external URLs when not in a request context.
+
+ Default: ``'http'``
+
+.. py:data:: MAX_CONTENT_LENGTH
+
+ Don't read more than this many bytes from the incoming request data. If not
+ set and the request does not specify a ``CONTENT_LENGTH``, no data will be
+ read for security.
+
+ Default: ``None``
+
+.. py:data:: JSON_AS_ASCII
+
+ Serialize objects to ASCII-encoded JSON. If this is disabled, the JSON
+ will be returned as a Unicode string, or encoded as ``UTF-8`` by
+ ``jsonify``. This has security implications when rendering the JSON in
+ to JavaScript in templates, and should typically remain enabled.
+
+ Default: ``True``
+
+.. py:data:: JSON_SORT_KEYS
+
+ Sort the keys of JSON objects alphabetically. This is useful for caching
+ because it ensures the data is serialized the same way no matter what
+ Python's hash seed is. While not recommended, you can disable this for a
+ possible performance improvement at the cost of caching.
+
+ Default: ``True``
+
+.. py:data:: JSONIFY_PRETTYPRINT_REGULAR
+
+ ``jsonify`` responses will be output with newlines, spaces, and indentation
+ for easier reading by humans. Always enabled in debug mode.
+
+ Default: ``False``
+
+.. py:data:: JSONIFY_MIMETYPE
+
+ The mimetype of ``jsonify`` responses.
+
+ Default: ``'application/json'``
+
+.. py:data:: TEMPLATES_AUTO_RELOAD
+
+ Reload templates when they are changed. If not set, it will be enabled in
+ debug mode.
+
+ Default: ``None``
+
+.. py:data:: EXPLAIN_TEMPLATE_LOADING
+
+ Log debugging information tracing how a template file was loaded. This can
+ be useful to figure out why a template was not loaded or the wrong file
+ appears to be loaded.
+
+ Default: ``False``
.. versionadded:: 0.4
``LOGGER_NAME``
@@ -245,6 +370,17 @@ The following configuration values are used internally by Flask:
``SESSION_REFRESH_EACH_REQUEST``, ``TEMPLATES_AUTO_RELOAD``,
``LOGGER_HANDLER_POLICY``, ``EXPLAIN_TEMPLATE_LOADING``
+.. versionchanged:: 1.0
+ ``LOGGER_NAME`` and ``LOGGER_HANDLER_POLICY`` were removed. See
+ :ref:`logging` for information about configuration.
+
+ Added :data:`ENV` to reflect the :envvar:`FLASK_ENV` environment
+ variable.
+
+ Added :data:`SESSION_COOKIE_SAMESITE` to control the session
+ cookie's ``SameSite`` option.
+
+
Configuring from Files
----------------------
@@ -262,7 +398,7 @@ So a common pattern is this::
This first loads the configuration from the
`yourapplication.default_settings` module and then overrides the values
-with the contents of the file the :envvar:``YOURAPPLICATION_SETTINGS``
+with the contents of the file the :envvar:`YOURAPPLICATION_SETTINGS`
environment variable points to. This environment variable can be set on
Linux or OS X with the export command in the shell before starting the
server::
@@ -284,7 +420,7 @@ Here is an example of a configuration file::
# Example configuration
DEBUG = False
- SECRET_KEY = '?\xbf,\xb4\x8d\xa3"<\x9c\xb0@\x0f5\xab,w\xee\x8d$0\x13\x8b83'
+ SECRET_KEY = b'_5#y2L"F4Q8z\n\xec]/'
Make sure to load the configuration very early on, so that extensions have
the ability to access the configuration when starting up. There are other
@@ -292,6 +428,54 @@ methods on the config object as well to load from individual files. For a
complete reference, read the :class:`~flask.Config` object's
documentation.
+Configuring from Environment Variables
+--------------------------------------
+
+In addition to pointing to configuration files using environment variables, you
+may find it useful (or necessary) to control your configuration values directly
+from the environment.
+
+Environment variables can be set on Linux or OS X with the export command in
+the shell before starting the server::
+
+ $ export SECRET_KEY='5f352379324c22463451387a0aec5d2f'
+ $ export DEBUG=False
+ $ python run-app.py
+ * Running on http://127.0.0.1:5000/
+ * Restarting with reloader...
+
+On Windows systems use the `set` builtin instead::
+
+ >set SECRET_KEY='5f352379324c22463451387a0aec5d2f'
+ >set DEBUG=False
+
+While this approach is straightforward to use, it is important to remember that
+environment variables are strings -- they are not automatically deserialized
+into Python types.
+
+Here is an example of a configuration file that uses environment variables::
+
+ # Example configuration
+ import os
+
+ ENVIRONMENT_DEBUG = os.environ.get("DEBUG", default=False)
+ if ENVIRONMENT_DEBUG.lower() in ("f", "false"):
+ ENVIRONMENT_DEBUG = False
+
+ DEBUG = ENVIRONMENT_DEBUG
+ SECRET_KEY = os.environ.get("SECRET_KEY", default=None)
+ if not SECRET_KEY:
+ raise ValueError("No secret key set for Flask application")
+
+
+Notice that any value besides an empty string will be interpreted as a boolean
+``True`` value in Python, which requires care if an environment explicitly sets
+values intended to be ``False``.
+
+Make sure to load the configuration very early on, so that extensions have the
+ability to access the configuration when starting up. There are other methods
+on the config object as well to load from individual files. For a complete
+reference, read the :class:`~flask.Config` class documentation.
Configuration Best Practices
----------------------------
@@ -344,7 +528,7 @@ configuration::
class Config(object):
DEBUG = False
TESTING = False
- DATABASE_URI = 'sqlite://:memory:'
+ DATABASE_URI = 'sqlite:///:memory:'
class ProductionConfig(Config):
DATABASE_URI = 'mysql://user@localhost/foo'
diff --git a/docs/contents.rst.inc b/docs/contents.rst.inc
index 8b25e61d..f76b1591 100644
--- a/docs/contents.rst.inc
+++ b/docs/contents.rst.inc
@@ -16,6 +16,7 @@ instructions for web development with Flask.
templating
testing
errorhandling
+ logging
config
signals
views
@@ -55,7 +56,7 @@ Design notes, legal information and changelog are here for the interested.
unicode
extensiondev
styleguide
- python3
upgrading
changelog
license
+ contributing
diff --git a/docs/contributing.rst b/docs/contributing.rst
new file mode 100644
index 00000000..e582053e
--- /dev/null
+++ b/docs/contributing.rst
@@ -0,0 +1 @@
+.. include:: ../CONTRIBUTING.rst
diff --git a/docs/deploying/fastcgi.rst b/docs/deploying/fastcgi.rst
index c0beae0c..46706033 100644
--- a/docs/deploying/fastcgi.rst
+++ b/docs/deploying/fastcgi.rst
@@ -111,7 +111,7 @@ Set yourapplication.fcgi::
#!/usr/bin/python
#: optional path to your local python site-packages folder
import sys
- sys.path.insert(0, '/lib/python2.6/site-packages')
+ sys.path.insert(0, '/lib/python/site-packages')
from flup.server.fcgi import WSGIServer
from yourapplication import app
@@ -144,7 +144,7 @@ A basic FastCGI configuration for lighttpd looks like that::
)
alias.url = (
- "/static/" => "/path/to/your/static"
+ "/static/" => "/path/to/your/static/"
)
url.rewrite-once = (
@@ -159,7 +159,7 @@ work in the URL root you have to work around a lighttpd bug with the
Make sure to apply it only if you are mounting the application the URL
root. Also, see the Lighty docs for more information on `FastCGI and Python
-`_ (note that
+`_ (note that
explicitly passing a socket to run() is no longer necessary).
Configuring nginx
@@ -234,7 +234,7 @@ python path. Common problems are:
web server.
- Different python interpreters being used.
-.. _nginx: http://nginx.org/
-.. _lighttpd: http://www.lighttpd.net/
+.. _nginx: https://nginx.org/
+.. _lighttpd: https://www.lighttpd.net/
.. _cherokee: http://cherokee-project.com/
.. _flup: https://pypi.python.org/pypi/flup
diff --git a/docs/deploying/index.rst b/docs/deploying/index.rst
index 5d88cf72..edf5a256 100644
--- a/docs/deploying/index.rst
+++ b/docs/deploying/index.rst
@@ -4,9 +4,8 @@ Deployment Options
==================
While lightweight and easy to use, **Flask's built-in server is not suitable
-for production** as it doesn't scale well and by default serves only one
-request at a time. Some of the options available for properly running Flask in
-production are documented here.
+for production** as it doesn't scale well. Some of the options available for
+properly running Flask in production are documented here.
If you want to deploy your Flask application to a WSGI server not listed here,
look up the server documentation about how to use a WSGI app with it. Just
@@ -20,9 +19,11 @@ Hosted options
- `Deploying Flask on Heroku `_
- `Deploying Flask on OpenShift `_
- `Deploying Flask on Webfaction `_
-- `Deploying Flask on Google App Engine `_
+- `Deploying Flask on Google App Engine `_
+- `Deploying Flask on AWS Elastic Beanstalk `_
- `Sharing your Localhost Server with Localtunnel `_
- `Deploying on Azure (IIS) `_
+- `Deploying on PythonAnywhere `_
Self-hosted options
-------------------
@@ -30,8 +31,8 @@ Self-hosted options
.. toctree::
:maxdepth: 2
- mod_wsgi
wsgi-standalone
uwsgi
+ mod_wsgi
fastcgi
cgi
diff --git a/docs/deploying/mod_wsgi.rst b/docs/deploying/mod_wsgi.rst
index 0f4af6c3..ca694b7d 100644
--- a/docs/deploying/mod_wsgi.rst
+++ b/docs/deploying/mod_wsgi.rst
@@ -13,7 +13,7 @@ If you are using the `Apache`_ webserver, consider using `mod_wsgi`_.
not called because this will always start a local WSGI server which
we do not want if we deploy that application to mod_wsgi.
-.. _Apache: http://httpd.apache.org/
+.. _Apache: https://httpd.apache.org/
Installing `mod_wsgi`
---------------------
@@ -114,7 +114,7 @@ refuse to run with the above configuration. On a Windows system, eliminate those
Note: There have been some changes in access control configuration for `Apache 2.4`_.
-.. _Apache 2.4: http://httpd.apache.org/docs/trunk/upgrading.html
+.. _Apache 2.4: https://httpd.apache.org/docs/trunk/upgrading.html
Most notably, the syntax for directory permissions has changed from httpd 2.2
@@ -133,9 +133,9 @@ to httpd 2.4 syntax
For more information consult the `mod_wsgi documentation`_.
.. _mod_wsgi: https://github.com/GrahamDumpleton/mod_wsgi
-.. _installation instructions: http://modwsgi.readthedocs.io/en/develop/installation.html
+.. _installation instructions: https://modwsgi.readthedocs.io/en/develop/installation.html
.. _virtual python: https://pypi.python.org/pypi/virtualenv
-.. _mod_wsgi documentation: http://modwsgi.readthedocs.io/en/develop/index.html
+.. _mod_wsgi documentation: https://modwsgi.readthedocs.io/en/develop/index.html
Troubleshooting
---------------
diff --git a/docs/deploying/uwsgi.rst b/docs/deploying/uwsgi.rst
index fc991e72..50c85fb2 100644
--- a/docs/deploying/uwsgi.rst
+++ b/docs/deploying/uwsgi.rst
@@ -66,7 +66,7 @@ to have it in the URL root its a bit simpler::
uwsgi_pass unix:/tmp/yourapplication.sock;
}
-.. _nginx: http://nginx.org/
-.. _lighttpd: http://www.lighttpd.net/
+.. _nginx: https://nginx.org/
+.. _lighttpd: https://www.lighttpd.net/
.. _cherokee: http://cherokee-project.com/
.. _uwsgi: http://projects.unbit.it/uwsgi/
diff --git a/docs/deploying/wsgi-standalone.rst b/docs/deploying/wsgi-standalone.rst
index ad43c144..5b0740a6 100644
--- a/docs/deploying/wsgi-standalone.rst
+++ b/docs/deploying/wsgi-standalone.rst
@@ -27,6 +27,22 @@ For example, to run a Flask application with 4 worker processes (``-w
.. _eventlet: http://eventlet.net/
.. _greenlet: https://greenlet.readthedocs.io/en/latest/
+uWSGI
+--------
+
+`uWSGI`_ is a fast application server written in C. It is very configurable
+which makes it more complicated to setup than gunicorn.
+
+Running `uWSGI HTTP Router`_::
+
+ uwsgi --http 127.0.0.1:5000 --module myproject:app
+
+For a more optimized setup, see `configuring uWSGI and NGINX`_.
+
+.. _uWSGI: http://uwsgi-docs.readthedocs.io/en/latest/
+.. _uWSGI HTTP Router: http://uwsgi-docs.readthedocs.io/en/latest/HTTP.html#the-uwsgi-http-https-router
+.. _configuring uWSGI and NGINX: uwsgi.html#starting-your-app-with-uwsgi
+
Gevent
-------
@@ -62,7 +78,7 @@ as well; see ``twistd -h`` and ``twistd web -h`` for more information. For
example, to run a Twisted Web server in the foreground, on port 8080, with an
application from ``myproject``::
- twistd -n web --port 8080 --wsgi myproject.app
+ twistd -n web --port tcp:8080 --wsgi myproject.app
.. _Twisted: https://twistedmatrix.com/
.. _Twisted Web: https://twistedmatrix.com/trac/wiki/TwistedWeb
diff --git a/docs/errorhandling.rst b/docs/errorhandling.rst
index 3bda5f15..4c260112 100644
--- a/docs/errorhandling.rst
+++ b/docs/errorhandling.rst
@@ -34,7 +34,7 @@ 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
-`_ for dealing with application errors. It's
+`_ for dealing with application errors. It's
available as an Open Source project `on GitHub
`__ and is also available as a `hosted version
`_ which you can try for free. Sentry
@@ -42,9 +42,9 @@ 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 `raven` client::
+To use Sentry you need to install the `raven` client with extra `flask` dependencies::
- $ pip install raven
+ $ pip install raven[flask]
And then add this to your Flask app::
@@ -76,256 +76,78 @@ Error handlers
You might want to show custom error pages to the user when an error occurs.
This can be done by registering error handlers.
-Error handlers are normal :ref:`views` but instead of being registered for
-routes, they are registered for exceptions that are raised while trying to
-do something else.
+An error handler is a normal view function that return a response, but instead
+of being registered for a route, it is registered for an exception or HTTP
+status code that would is raised while trying to handle a request.
Registering
```````````
-Register error handlers using :meth:`~flask.Flask.errorhandler` or
-:meth:`~flask.Flask.register_error_handler`::
+Register handlers by decorating a function with
+:meth:`~flask.Flask.errorhandler`. Or use
+:meth:`~flask.Flask.register_error_handler` to register the function later.
+Remember to set the error code when returning the response. ::
@app.errorhandler(werkzeug.exceptions.BadRequest)
def handle_bad_request(e):
- return 'bad request!'
-
- app.register_error_handler(400, lambda e: 'bad request!')
+ return 'bad request!', 400
+
+ # or, without the decorator
+ app.register_error_handler(400, handle_bad_request)
-Those two ways are equivalent, but the first one is more clear and leaves
-you with a function to call on your whim (and in tests). Note that
:exc:`werkzeug.exceptions.HTTPException` subclasses like
-:exc:`~werkzeug.exceptions.BadRequest` from the example and their HTTP codes
-are interchangeable when handed to the registration methods or decorator
-(``BadRequest.code == 400``).
+:exc:`~werkzeug.exceptions.BadRequest` and their HTTP codes are interchangeable
+when registering handlers. (``BadRequest.code == 400``)
-You are however not limited to :exc:`~werkzeug.exceptions.HTTPException`
-or HTTP status codes but can register a handler for every exception class you
-like.
+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. ::
-.. versionchanged:: 0.11
+ class InsufficientStorage(werkzeug.exceptions.HTTPException):
+ code = 507
+ description = 'Not enough storage space.'
+
+ app.register_error_handler(InsuffcientStorage, handle_507)
- Errorhandlers are now prioritized by specificity of the exception classes
- they are registered for instead of the order they are registered in.
+ raise InsufficientStorage()
+
+Handlers can be registered for any exception class, not just
+:exc:`~werkzeug.exceptions.HTTPException` subclasses or HTTP status
+codes. Handlers can be registered for a specific class, or for all subclasses
+of a parent class.
Handling
````````
-Once an exception instance is raised, its class hierarchy is traversed,
-and searched for in the exception classes for which handlers are registered.
-The most specific handler is selected.
+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.
-E.g. if an instance of :exc:`ConnectionRefusedError` is raised, and a handler
+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 on the
-exception instance, and its response is shown to the user.
-
-Error Mails
------------
-
-If the application runs in production mode (which it will do on your
-server) you might not see any log messages. The reason for that is that
-Flask by default will just report to the WSGI error stream or stderr
-(depending on what's available). Where this ends up is sometimes hard to
-find. Often it's in your webserver's log files.
-
-I can pretty much promise you however that if you only use a logfile for
-the application errors you will never look at it except for debugging an
-issue when a user reported it for you. What you probably want instead is
-a mail the second the exception happened. Then you get an alert and you
-can do something about it.
-
-Flask uses the Python builtin logging system, and it can actually send
-you mails for errors which is probably what you want. Here is how you can
-configure the Flask logger to send you mails for exceptions::
-
- ADMINS = ['yourname@example.com']
- if not app.debug:
- import logging
- from logging.handlers import SMTPHandler
- mail_handler = SMTPHandler('127.0.0.1',
- 'server-error@example.com',
- ADMINS, 'YourApplication Failed')
- mail_handler.setLevel(logging.ERROR)
- app.logger.addHandler(mail_handler)
-
-So what just happened? We created a new
-:class:`~logging.handlers.SMTPHandler` that will send mails with the mail
-server listening on ``127.0.0.1`` to all the `ADMINS` from the address
-*server-error@example.com* with the subject "YourApplication Failed". If
-your mail server requires credentials, these can also be provided. For
-that check out the documentation for the
-:class:`~logging.handlers.SMTPHandler`.
-
-We also tell the handler to only send errors and more critical messages.
-Because we certainly don't want to get a mail for warnings or other
-useless logs that might happen during request handling.
-
-Before you run that in production, please also look at :ref:`logformat` to
-put more information into that error mail. That will save you from a lot
-of frustration.
-
-
-Logging to a File
------------------
-
-Even if you get mails, you probably also want to log warnings. It's a
-good idea to keep as much information around that might be required to
-debug a problem. By default as of Flask 0.11, errors are logged to your
-webserver's log automatically. Warnings however are not. Please note
-that Flask itself will not issue any warnings in the core system, so it's
-your responsibility to warn in the code if something seems odd.
-
-There are a couple of handlers provided by the logging system out of the
-box but not all of them are useful for basic error logging. The most
-interesting are probably the following:
-
-- :class:`~logging.FileHandler` - logs messages to a file on the
- filesystem.
-- :class:`~logging.handlers.RotatingFileHandler` - logs messages to a file
- on the filesystem and will rotate after a certain number of messages.
-- :class:`~logging.handlers.NTEventLogHandler` - will log to the system
- event log of a Windows system. If you are deploying on a Windows box,
- this is what you want to use.
-- :class:`~logging.handlers.SysLogHandler` - sends logs to a UNIX
- syslog.
-
-Once you picked your log handler, do like you did with the SMTP handler
-above, just make sure to use a lower setting (I would recommend
-`WARNING`)::
-
- if not app.debug:
- import logging
- from themodule import TheHandlerYouWant
- file_handler = TheHandlerYouWant(...)
- file_handler.setLevel(logging.WARNING)
- app.logger.addHandler(file_handler)
-
-.. _logformat:
-
-Controlling the Log Format
---------------------------
-
-By default a handler will only write the message string into a file or
-send you that message as mail. A log record stores more information,
-and it makes a lot of sense to configure your logger to also contain that
-information so that you have a better idea of why that error happened, and
-more importantly, where it did.
-
-A formatter can be instantiated with a format string. Note that
-tracebacks are appended to the log entry automatically. You don't have to
-do that in the log formatter format string.
-
-Here some example setups:
-
-Email
-`````
-
-::
-
- from logging import Formatter
- mail_handler.setFormatter(Formatter('''
- Message type: %(levelname)s
- Location: %(pathname)s:%(lineno)d
- Module: %(module)s
- Function: %(funcName)s
- Time: %(asctime)s
-
- Message:
-
- %(message)s
- '''))
-
-File logging
-````````````
-
-::
-
- from logging import Formatter
- file_handler.setFormatter(Formatter(
- '%(asctime)s %(levelname)s: %(message)s '
- '[in %(pathname)s:%(lineno)d]'
- ))
-
-
-Complex Log Formatting
-``````````````````````
-
-Here is a list of useful formatting variables for the format string. Note
-that this list is not complete, consult the official documentation of the
-:mod:`logging` package for a full list.
-
-.. tabularcolumns:: |p{3cm}|p{12cm}|
-
-+------------------+----------------------------------------------------+
-| Format | Description |
-+==================+====================================================+
-| ``%(levelname)s``| Text logging level for the message |
-| | (``'DEBUG'``, ``'INFO'``, ``'WARNING'``, |
-| | ``'ERROR'``, ``'CRITICAL'``). |
-+------------------+----------------------------------------------------+
-| ``%(pathname)s`` | Full pathname of the source file where the |
-| | logging call was issued (if available). |
-+------------------+----------------------------------------------------+
-| ``%(filename)s`` | Filename portion of pathname. |
-+------------------+----------------------------------------------------+
-| ``%(module)s`` | Module (name portion of filename). |
-+------------------+----------------------------------------------------+
-| ``%(funcName)s`` | Name of function containing the logging call. |
-+------------------+----------------------------------------------------+
-| ``%(lineno)d`` | Source line number where the logging call was |
-| | issued (if available). |
-+------------------+----------------------------------------------------+
-| ``%(asctime)s`` | Human-readable time when the LogRecord` was |
-| | created. By default this is of the form |
-| | ``"2003-07-08 16:49:45,896"`` (the numbers after |
-| | the comma are millisecond portion of the time). |
-| | This can be changed by subclassing the formatter |
-| | and overriding the |
-| | :meth:`~logging.Formatter.formatTime` method. |
-+------------------+----------------------------------------------------+
-| ``%(message)s`` | The logged message, computed as ``msg % args`` |
-+------------------+----------------------------------------------------+
-
-If you want to further customize the formatting, you can subclass the
-formatter. The formatter has three interesting methods:
-
-:meth:`~logging.Formatter.format`:
- handles the actual formatting. It is passed a
- :class:`~logging.LogRecord` object and has to return the formatted
- string.
-:meth:`~logging.Formatter.formatTime`:
- called for `asctime` formatting. If you want a different time format
- you can override this method.
-:meth:`~logging.Formatter.formatException`
- called for exception formatting. It is passed an :attr:`~sys.exc_info`
- tuple and has to return a string. The default is usually fine, you
- don't have to override it.
-
-For more information, head over to the official documentation.
-
-
-Other Libraries
----------------
-
-So far we only configured the logger your application created itself.
-Other libraries might log themselves as well. For example, SQLAlchemy uses
-logging heavily in its core. While there is a method to configure all
-loggers at once in the :mod:`logging` package, I would not recommend using
-it. There might be a situation in which you want to have multiple
-separate applications running side by side in the same Python interpreter
-and then it becomes impossible to have different logging setups for those.
-
-Instead, I would recommend figuring out which loggers you are interested
-in, getting the loggers with the :func:`~logging.getLogger` function and
-iterating over them to attach handlers::
-
- from logging import getLogger
- loggers = [app.logger, getLogger('sqlalchemy'),
- getLogger('otherlibrary')]
- for logger in loggers:
- logger.addHandler(mail_handler)
- logger.addHandler(file_handler)
+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.
+
+.. versionchanged:: 0.11
+
+ Handlers are prioritized by specificity of the exception classes they are
+ registered for instead of the order they are registered in.
+
+Logging
+-------
+
+See :ref:`logging` for information on how to log exceptions, such as by
+emailing them to admins.
Debugging Application Errors
diff --git a/docs/extensiondev.rst b/docs/extensiondev.rst
index d73d6019..29c33f3c 100644
--- a/docs/extensiondev.rst
+++ b/docs/extensiondev.rst
@@ -29,12 +29,6 @@ be something like "Flask-SimpleXML". Make sure to include the name
This is how users can then register dependencies to your extension in
their :file:`setup.py` files.
-Flask sets up a redirect package called :data:`flask.ext` where users
-should import the extensions from. If you for instance have a package
-called ``flask_something`` users would import it as
-``flask.ext.something``. This is done to transition from the old
-namespace packages. See :ref:`ext-import-transition` for more details.
-
But what do extensions look like themselves? An extension has to ensure
that it works with multiple Flask application instances at once. This is
a requirement because many people will use patterns like the
@@ -48,7 +42,7 @@ that people can easily install the development version into their
virtualenv without having to download the library by hand.
Flask extensions must be licensed under a BSD, MIT or more liberal license
-to be able to be enlisted in the Flask Extension Registry. Keep in mind
+in order to be listed in the Flask Extension Registry. Keep in mind
that the Flask Extension Registry is a moderated place and libraries will
be reviewed upfront if they behave as required.
@@ -154,10 +148,10 @@ What to use depends on what you have in mind. For the SQLite 3 extension
we will use the class-based approach because it will provide users with an
object that handles opening and closing database connections.
-What's important about classes is that they encourage to be shared around
-on module level. In that case, the object itself must not under any
+When designing your classes, it's important to make them easily reusable
+at the module level. This means the object itself must not under any
circumstances store any application specific state and must be shareable
-between different application.
+between different applications.
The Extension Code
------------------
@@ -334,10 +328,10 @@ development. If you want to learn more, it's a very good idea to check
out existing extensions on the `Flask Extension Registry`_. If you feel
lost there is still the `mailinglist`_ and the `IRC channel`_ to get some
ideas for nice looking APIs. Especially if you do something nobody before
-you did, it might be a very good idea to get some more input. This not
-only to get an idea about what people might want to have from an
-extension, but also to avoid having multiple developers working on pretty
-much the same side by side.
+you did, it might be a very good idea to get some more input. This not only
+generates useful feedback on what people might want from an extension, but
+also avoids having multiple developers working in isolation on pretty much the
+same problem.
Remember: good API design is hard, so introduce your project on the
mailinglist, and let other developers give you a helping hand with
@@ -370,10 +364,10 @@ extension to be approved you have to follow these guidelines:
3. APIs of approved extensions will be checked for the following
characteristics:
- - an approved extension has to support multiple applications
- running in the same Python process.
- - it must be possible to use the factory pattern for creating
- applications.
+ - an approved extension has to support multiple applications
+ running in the same Python process.
+ - it must be possible to use the factory pattern for creating
+ applications.
4. The license must be BSD/MIT/WTFPL licensed.
5. The naming scheme for official extensions is *Flask-ExtensionName* or
@@ -387,13 +381,11 @@ extension to be approved you have to follow these guidelines:
link to the documentation, website (if there is one) and there
must be a link to automatically install the development version
(``PackageName==dev``).
-9. The ``zip_safe`` flag in the setup script must be set to ``False``,
- even if the extension would be safe for zipping.
-10. An extension currently has to support Python 2.6 as well as
- Python 2.7
+9. The ``zip_safe`` flag in the setup script must be set to ``False``,
+ even if the extension would be safe for zipping.
+10. An extension currently has to support Python 3.4 and newer and 2.7.
-.. _ext-import-transition:
Extension Import Transition
---------------------------
@@ -413,6 +405,6 @@ schema. The ``flask.ext.foo`` compatibility alias is still in Flask 0.11 but is
now deprecated -- you should use ``flask_foo``.
-.. _OAuth extension: http://pythonhosted.org/Flask-OAuth/
+.. _OAuth extension: https://pythonhosted.org/Flask-OAuth/
.. _mailinglist: http://flask.pocoo.org/mailinglist/
.. _IRC channel: http://flask.pocoo.org/community/irc/
diff --git a/docs/flaskext.py b/docs/flaskext.py
deleted file mode 100644
index 33f47449..00000000
--- a/docs/flaskext.py
+++ /dev/null
@@ -1,86 +0,0 @@
-# flasky extensions. flasky pygments style based on tango style
-from pygments.style import Style
-from pygments.token import Keyword, Name, Comment, String, Error, \
- Number, Operator, Generic, Whitespace, Punctuation, Other, Literal
-
-
-class FlaskyStyle(Style):
- background_color = "#f8f8f8"
- default_style = ""
-
- styles = {
- # No corresponding class for the following:
- #Text: "", # class: ''
- Whitespace: "underline #f8f8f8", # class: 'w'
- Error: "#a40000 border:#ef2929", # class: 'err'
- Other: "#000000", # class 'x'
-
- Comment: "italic #8f5902", # class: 'c'
- Comment.Preproc: "noitalic", # class: 'cp'
-
- Keyword: "bold #004461", # class: 'k'
- Keyword.Constant: "bold #004461", # class: 'kc'
- Keyword.Declaration: "bold #004461", # class: 'kd'
- Keyword.Namespace: "bold #004461", # class: 'kn'
- Keyword.Pseudo: "bold #004461", # class: 'kp'
- Keyword.Reserved: "bold #004461", # class: 'kr'
- Keyword.Type: "bold #004461", # class: 'kt'
-
- Operator: "#582800", # class: 'o'
- Operator.Word: "bold #004461", # class: 'ow' - like keywords
-
- Punctuation: "bold #000000", # class: 'p'
-
- # because special names such as Name.Class, Name.Function, etc.
- # are not recognized as such later in the parsing, we choose them
- # to look the same as ordinary variables.
- Name: "#000000", # class: 'n'
- Name.Attribute: "#c4a000", # class: 'na' - to be revised
- Name.Builtin: "#004461", # class: 'nb'
- Name.Builtin.Pseudo: "#3465a4", # class: 'bp'
- Name.Class: "#000000", # class: 'nc' - to be revised
- Name.Constant: "#000000", # class: 'no' - to be revised
- Name.Decorator: "#888", # class: 'nd' - to be revised
- Name.Entity: "#ce5c00", # class: 'ni'
- Name.Exception: "bold #cc0000", # class: 'ne'
- Name.Function: "#000000", # class: 'nf'
- Name.Property: "#000000", # class: 'py'
- Name.Label: "#f57900", # class: 'nl'
- Name.Namespace: "#000000", # class: 'nn' - to be revised
- Name.Other: "#000000", # class: 'nx'
- Name.Tag: "bold #004461", # class: 'nt' - like a keyword
- Name.Variable: "#000000", # class: 'nv' - to be revised
- Name.Variable.Class: "#000000", # class: 'vc' - to be revised
- Name.Variable.Global: "#000000", # class: 'vg' - to be revised
- Name.Variable.Instance: "#000000", # class: 'vi' - to be revised
-
- Number: "#990000", # class: 'm'
-
- Literal: "#000000", # class: 'l'
- Literal.Date: "#000000", # class: 'ld'
-
- String: "#4e9a06", # class: 's'
- String.Backtick: "#4e9a06", # class: 'sb'
- String.Char: "#4e9a06", # class: 'sc'
- String.Doc: "italic #8f5902", # class: 'sd' - like a comment
- String.Double: "#4e9a06", # class: 's2'
- String.Escape: "#4e9a06", # class: 'se'
- String.Heredoc: "#4e9a06", # class: 'sh'
- String.Interpol: "#4e9a06", # class: 'si'
- String.Other: "#4e9a06", # class: 'sx'
- String.Regex: "#4e9a06", # class: 'sr'
- String.Single: "#4e9a06", # class: 's1'
- String.Symbol: "#4e9a06", # class: 'ss'
-
- Generic: "#000000", # class: 'g'
- Generic.Deleted: "#a40000", # class: 'gd'
- Generic.Emph: "italic #000000", # class: 'ge'
- Generic.Error: "#ef2929", # class: 'gr'
- Generic.Heading: "bold #000080", # class: 'gh'
- Generic.Inserted: "#00A000", # class: 'gi'
- Generic.Output: "#888", # class: 'go'
- Generic.Prompt: "#745334", # class: 'gp'
- Generic.Strong: "bold #000000", # class: 'gs'
- Generic.Subheading: "bold #800080", # class: 'gu'
- Generic.Traceback: "bold #a40000", # class: 'gt'
- }
diff --git a/docs/installation.rst b/docs/installation.rst
index 6f833eac..88b9af09 100644
--- a/docs/installation.rst
+++ b/docs/installation.rst
@@ -3,163 +3,179 @@
Installation
============
-Flask depends on some external libraries, like `Werkzeug
-`_ and `Jinja2 `_.
-Werkzeug is a toolkit for WSGI, the standard Python interface between web
-applications and a variety of servers for both development and deployment.
-Jinja2 renders templates.
+Python Version
+--------------
-So how do you get all that on your computer quickly? There are many ways you
-could do that, but the most kick-ass method is virtualenv, so let's have a look
-at that first.
+We recommend using the latest version of Python 3. Flask supports Python 3.4
+and newer, Python 2.7, and PyPy.
-You will need Python 2.6 or newer to get started, so be sure to have an
-up-to-date Python 2.x installation. For using Flask with Python 3 have a
-look at :ref:`python3-support`.
+Dependencies
+------------
-.. _virtualenv:
+These distributions will be installed automatically when installing Flask.
-virtualenv
-----------
+* `Werkzeug`_ implements WSGI, the standard Python interface between
+ applications and servers.
+* `Jinja`_ is a template language that renders the pages your application
+ serves.
+* `MarkupSafe`_ comes with Jinja. It escapes untrusted input when rendering
+ templates to avoid injection attacks.
+* `ItsDangerous`_ securely signs data to ensure its integrity. This is used
+ to protect Flask's session cookie.
+* `Click`_ is a framework for writing command line applications. It provides
+ the ``flask`` command and allows adding custom management commands.
-Virtualenv is probably what you want to use during development, and if you have
-shell access to your production machines, you'll probably want to use it there,
-too.
+.. _Werkzeug: http://werkzeug.pocoo.org/
+.. _Jinja: http://jinja.pocoo.org/
+.. _MarkupSafe: https://pypi.python.org/pypi/MarkupSafe
+.. _ItsDangerous: https://pythonhosted.org/itsdangerous/
+.. _Click: http://click.pocoo.org/
-What problem does virtualenv solve? If you like Python as much as I do,
-chances are you want to use it for other projects besides Flask-based web
-applications. But the more projects you have, the more likely it is that you
-will be working with different versions of Python itself, or at least different
-versions of Python libraries. Let's face it: quite often libraries break
-backwards compatibility, and it's unlikely that any serious application will
-have zero dependencies. So what do you do if two or more of your projects have
-conflicting dependencies?
+Optional dependencies
+~~~~~~~~~~~~~~~~~~~~~
-Virtualenv to the rescue! Virtualenv enables multiple side-by-side
-installations of Python, one for each project. It doesn't actually install
-separate copies of Python, but it does provide a clever way to keep different
-project environments isolated. Let's see how virtualenv works.
+These distributions will not be installed automatically. Flask will detect and
+use them if you install them.
-If you are on Mac OS X or Linux, chances are that the following
-command will work for you::
+* `Blinker`_ provides support for :ref:`signals`.
+* `SimpleJSON`_ is a fast JSON implementation that is compatible with
+ Python's ``json`` module. It is preferred for JSON operations if it is
+ installed.
+* `python-dotenv`_ enables support for :ref:`dotenv` when running ``flask``
+ commands.
+* `Watchdog`_ provides a faster, more efficient reloader for the development
+ server.
- $ sudo pip install virtualenv
+.. _Blinker: https://pythonhosted.org/blinker/
+.. _SimpleJSON: https://simplejson.readthedocs.io/
+.. _python-dotenv: https://github.com/theskumar/python-dotenv#readme
+.. _watchdog: https://pythonhosted.org/watchdog/
-It will probably install virtualenv on your system. Maybe it's even
-in your package manager. If you use Ubuntu, try::
+Virtual environments
+--------------------
- $ sudo apt-get install python-virtualenv
+Use a virtual environment to manage the dependencies for your project, both in
+development and in production.
-If you are on Windows and don't have the ``easy_install`` command, you must
-install it first. Check the :ref:`windows-easy-install` section for more
-information about how to do that. Once you have it installed, run the same
-commands as above, but without the ``sudo`` prefix.
+What problem does a virtual environment solve? The more Python projects you
+have, the more likely it is that you need to work with different versions of
+Python libraries, or even Python itself. Newer versions of libraries for one
+project can break compatibility in another project.
-Once you have virtualenv installed, just fire up a shell and create
-your own environment. I usually create a project folder and a :file:`venv`
-folder within::
+Virtual environments are independent groups of Python libraries, one for each
+project. Packages installed for one project will not affect other projects or
+the operating system's packages.
- $ mkdir myproject
- $ cd myproject
- $ virtualenv venv
- New python executable in venv/bin/python
- Installing setuptools, pip............done.
+Python 3 comes bundled with the :mod:`venv` module to create virtual
+environments. If you're using a modern version of Python, you can continue on
+to the next section.
-Now, whenever you want to work on a project, you only have to activate the
-corresponding environment. On OS X and Linux, do the following::
+If you're using Python 2, see :ref:`install-install-virtualenv` first.
- $ . venv/bin/activate
+.. _install-create-env:
-If you are a Windows user, the following command is for you::
+Create an environment
+~~~~~~~~~~~~~~~~~~~~~
- $ venv\Scripts\activate
+Create a project folder and a :file:`venv` folder within:
-Either way, you should now be using your virtualenv (notice how the prompt of
-your shell has changed to show the active environment).
+.. code-block:: sh
-And if you want to go back to the real world, use the following command::
+ mkdir myproject
+ cd myproject
+ python3 -m venv venv
- $ deactivate
+On Windows:
-After doing this, the prompt of your shell should be as familiar as before.
+.. code-block:: bat
-Now, let's move on. Enter the following command to get Flask activated in your
-virtualenv::
+ py -3 -m venv venv
- $ pip install Flask
+If you needed to install virtualenv because you are on an older version of
+Python, use the following command instead:
-A few seconds later and you are good to go.
+.. code-block:: sh
+ virtualenv venv
-System-Wide Installation
-------------------------
+On Windows:
-This is possible as well, though I do not recommend it. Just run
-``pip`` with root privileges::
+.. code-block:: bat
- $ sudo pip install Flask
+ \Python27\Scripts\virtualenv.exe venv
-(On Windows systems, run it in a command-prompt window with administrator
-privileges, and leave out ``sudo``.)
+Activate the environment
+~~~~~~~~~~~~~~~~~~~~~~~~
+Before you work on your project, activate the corresponding environment:
-Living on the Edge
-------------------
+.. code-block:: sh
+
+ . venv/bin/activate
+
+On Windows:
+
+.. code-block:: bat
+
+ venv\Scripts\activate
+
+Your shell prompt will change to show the name of the activated environment.
+
+Install Flask
+-------------
-If you want to work with the latest version of Flask, there are two ways: you
-can either let ``pip`` pull in the development version, or you can tell
-it to operate on a git checkout. Either way, virtualenv is recommended.
+Within the activated environment, use the following command to install Flask:
-Get the git checkout in a new virtualenv and run in development mode::
+.. code-block:: sh
- $ git clone http://github.com/pallets/flask.git
- Initialized empty Git repository in ~/dev/flask/.git/
- $ cd flask
- $ virtualenv venv
- New python executable in venv/bin/python
- Installing setuptools, pip............done.
- $ . venv/bin/activate
- $ python setup.py develop
- ...
- Finished processing dependencies for Flask
+ pip install Flask
+
+Living on the edge
+~~~~~~~~~~~~~~~~~~
+
+If you want to work with the latest Flask code before it's released, install or
+update the code from the master branch:
+
+.. code-block:: sh
+
+ pip install -U https://github.com/pallets/flask/archive/master.tar.gz
+
+.. _install-install-virtualenv:
+
+Install virtualenv
+------------------
-This will pull in the dependencies and activate the git head as the current
-version inside the virtualenv. Then all you have to do is run ``git pull
-origin`` to update to the latest version.
+If you are using Python 2, the venv module is not available. Instead,
+install `virtualenv`_.
-.. _windows-easy-install:
+On Linux, virtualenv is provided by your package manager:
-`pip` and `setuptools` on Windows
----------------------------------
+.. code-block:: sh
-Sometimes getting the standard "Python packaging tools" like ``pip``, ``setuptools``
-and ``virtualenv`` can be a little trickier, but nothing very hard. The crucial
-package you will need is pip - this will let you install
-anything else (like virtualenv). Fortunately there is a "bootstrap script"
-you can run to install.
+ # Debian, Ubuntu
+ sudo apt-get install python-virtualenv
-If you don't currently have ``pip``, then `get-pip.py` will install it for you.
+ # CentOS, Fedora
+ sudo yum install python-virtualenv
-`get-pip.py`_
+ # Arch
+ sudo pacman -S python-virtualenv
-It should be double-clickable once you download it. If you already have ``pip``,
-you can upgrade them by running::
+If you are on Mac OS X or Windows, download `get-pip.py`_, then:
- > pip install --upgrade pip setuptools
+.. code-block:: sh
-Most often, once you pull up a command prompt you want to be able to type ``pip``
-and ``python`` which will run those things, but this might not automatically happen
-on Windows, because it doesn't know where those executables are (give either a try!).
+ sudo python2 Downloads/get-pip.py
+ sudo python2 -m pip install virtualenv
-To fix this, you should be able to navigate to your Python install directory
-(e.g :file:`C:\Python27`), then go to :file:`Tools`, then :file:`Scripts`, then find the
-:file:`win_add2path.py` file and run that. Open a **new** Command Prompt and
-check that you can now just type ``python`` to bring up the interpreter.
+On Windows, as an administrator:
-Finally, to install `virtualenv`_, you can simply run::
+.. code-block:: bat
- > pip install virtualenv
+ \Python27\python.exe Downloads\get-pip.py
+ \Python27\python.exe -m pip install virtualenv
-Then you can be off on your way following the installation instructions above.
+Now you can continue to :ref:`install-create-env`.
+.. _virtualenv: https://virtualenv.pypa.io/
.. _get-pip.py: https://bootstrap.pypa.io/get-pip.py
diff --git a/docs/logging.rst b/docs/logging.rst
new file mode 100644
index 00000000..36ed7c85
--- /dev/null
+++ b/docs/logging.rst
@@ -0,0 +1,175 @@
+.. _logging:
+
+Logging
+=======
+
+Flask uses standard Python :mod:`logging`. All Flask-related messages are
+logged under the ``'flask'`` logger namespace.
+:meth:`Flask.logger ` returns the logger named
+``'flask.app'``, and can be used to log messages for your application. ::
+
+ @app.route('/login', methods=['POST'])
+ def login():
+ user = get_user(request.form['username'])
+
+ if user.check_password(request.form['password']):
+ login_user(user)
+ app.logger.info('%s logged in successfully', user.username)
+ return redirect(url_for('index'))
+ else:
+ app.logger.info('%s failed to log in', user.username)
+ abort(401)
+
+
+Basic Configuration
+-------------------
+
+When you want to configure logging for your project, you should do it as soon
+as possible when the program starts. If :meth:`app.logger `
+is accessed before logging is configured, it will add a default handler. If
+possible, configure logging before creating the application object.
+
+This example uses :func:`~logging.config.dictConfig` to create a logging
+configuration similar to Flask's default, except for all logs::
+
+ from logging.config import dictConfig
+
+ dictConfig({
+ 'version': 1,
+ 'formatters': {'default': {
+ 'format': '[%(asctime)s] %(levelname)s in %(module)s: %(message)s',
+ }},
+ 'handlers': {'wsgi': {
+ 'class': 'logging.StreamHandler',
+ 'stream': 'ext://flask.logging.wsgi_errors_stream',
+ 'formatter': 'default'
+ }},
+ 'root': {
+ 'level': 'INFO',
+ 'handlers': ['wsgi']
+ }
+ })
+
+ app = Flask(__name__)
+
+
+Default Configuration
+`````````````````````
+
+If you do not configure logging yourself, Flask will add a
+:class:`~logging.StreamHandler` to :meth:`app.logger `
+automatically. During requests, it will write to the stream specified by the
+WSGI server in ``environ['wsgi.errors']`` (which is usually
+:data:`sys.stderr`). Outside a request, it will log to :data:`sys.stderr`.
+
+
+Removing the Default Handler
+````````````````````````````
+
+If you configured logging after accessing
+:meth:`app.logger `, and need to remove the default
+handler, you can import and remove it::
+
+ from flask.logging import default_handler
+
+ app.logger.removeHandler(default_handler)
+
+
+Email Errors to Admins
+----------------------
+
+When running the application on a remote server for production, you probably
+won't be looking at the log messages very often. The WSGI server will probably
+send log messages to a file, and you'll only check that file if a user tells
+you something went wrong.
+
+To be proactive about discovering and fixing bugs, you can configure a
+:class:`logging.handlers.SMTPHandler` to send an email when errors and higher
+are logged. ::
+
+ import logging
+ from logging.handlers import SMTPHandler
+
+ mail_handler = SMTPHandler(
+ mailhost='127.0.0.1',
+ fromaddr='server-error@example.com',
+ toaddrs=['admin@example.com'],
+ subject='Application Error'
+ )
+ mail_handler.setLevel(logging.ERROR)
+ mail_handler.setFormatter(logging.Formatter(
+ '[%(asctime)s] %(levelname)s in %(module)s: %(message)s'
+ ))
+
+ if not app.debug:
+ app.logger.addHandler(mail_handler)
+
+This requires that you have an SMTP server set up on the same server. See the
+Python docs for more information about configuring the handler.
+
+
+Injecting Request Information
+-----------------------------
+
+Seeing more information about the request, such as the IP address, may help
+debugging some errors. You can subclass :class:`logging.Formatter` to inject
+your own fields that can be used in messages. You can change the formatter for
+Flask's default handler, the mail handler defined above, or any other
+handler. ::
+
+ from flask import request
+ from flask.logging import default_handler
+
+ class RequestFormatter(logging.Formatter):
+ def format(self, record):
+ record.url = request.url
+ record.remote_addr = request.remote_addr
+ return super().format(record)
+
+ formatter = RequestFormatter(
+ '[%(asctime)s] %(remote_addr)s requested %(url)s\n'
+ '%(levelname)s in %(module)s: %(message)s'
+ )
+ default_handler.setFormatter(formatter)
+ mail_handler.setFormatter(formatter)
+
+
+Other Libraries
+---------------
+
+Other libraries may use logging extensively, and you want to see relevant
+messages from those logs too. The simplest way to do this is to add handlers
+to the root logger instead of only the app logger. ::
+
+ from flask.logging import default_handler
+
+ root = logging.getLogger()
+ root.addHandler(default_handler)
+ root.addHandler(mail_handler)
+
+Depending on your project, it may be more useful to configure each logger you
+care about separately, instead of configuring only the root logger. ::
+
+ for logger in (
+ app.logger,
+ logging.getLogger('sqlalchemy'),
+ logging.getLogger('other_package'),
+ ):
+ logger.addHandler(default_handler)
+ logger.addHandler(mail_handler)
+
+
+Werkzeug
+````````
+
+Werkzeug logs basic request/response information to the ``'werkzeug'`` logger.
+If the root logger has no handlers configured, Werkzeug adds a
+:class:`~logging.StreamHandler` to its logger.
+
+
+Flask Extensions
+````````````````
+
+Depending on the situation, an extension may choose to log to
+:meth:`app.logger ` or its own named logger. Consult each
+extension's documentation for details.
diff --git a/docs/patterns/appfactories.rst b/docs/patterns/appfactories.rst
index dc9660ae..3e880205 100644
--- a/docs/patterns/appfactories.rst
+++ b/docs/patterns/appfactories.rst
@@ -6,7 +6,7 @@ Application Factories
If you are already using packages and blueprints for your application
(:ref:`blueprints`) there are a couple of really nice ways to further improve
the experience. A common pattern is creating the application object when
-the blueprint is imported. But if you move the creation of this object,
+the blueprint is imported. But if you move the creation of this object
into a function, you can then create multiple instances of this app later.
So why would you want to do this?
@@ -60,7 +60,7 @@ Factories & Extensions
It's preferable to create your extensions and app factories so that the
extension object does not initially get bound to the application.
-Using `Flask-SQLAlchemy `_,
+Using `Flask-SQLAlchemy `_,
as an example, you should not do something along those lines::
def create_app(config_filename):
@@ -89,28 +89,29 @@ For more information about the design of extensions refer to :doc:`/extensiondev
Using Applications
------------------
-So to use such an application you then have to create the application
-first in a separate file otherwise the :command:`flask` command won't be able
-to find it. Here an example :file:`exampleapp.py` file that creates such
-an application::
+To run such an application, you can use the :command:`flask` command::
- from yourapplication import create_app
- app = create_app('/path/to/config.cfg')
-
-It can then be used with the :command:`flask` command::
+ export FLASK_APP=myapp
+ flask run
+
+Flask will automatically detect the factory (``create_app`` or ``make_app``)
+in ``myapp``. You can also pass arguments to the factory like this::
- export FLASK_APP=exampleapp
+ export FLASK_APP="myapp:create_app('dev')"
flask run
+
+Then the ``create_app`` factory in ``myapp`` is called with the string
+``'dev'`` as the argument. See :doc:`/cli` for more detail.
Factory Improvements
--------------------
-The factory function from above is not very clever so far, you can improve
-it. The following changes are straightforward and possible:
+The factory function above is not very clever, but you can improve it.
+The following changes are straightforward to implement:
-1. make it possible to pass in configuration values for unittests so that
- you don't have to create config files on the filesystem
-2. call a function from a blueprint when the application is setting up so
+1. Make it possible to pass in configuration values for unit tests so that
+ you don't have to create config files on the filesystem.
+2. Call a function from a blueprint when the application is setting up so
that you have a place to modify attributes of the application (like
- hooking in before / after request handlers etc.)
-3. Add in WSGI middlewares when the application is creating if necessary.
+ hooking in before/after request handlers etc.)
+3. Add in WSGI middlewares when the application is being created if necessary.
diff --git a/docs/patterns/celery.rst b/docs/patterns/celery.rst
index 673d953b..c3098a9e 100644
--- a/docs/patterns/celery.rst
+++ b/docs/patterns/celery.rst
@@ -1,24 +1,27 @@
-Celery Based Background Tasks
-=============================
+Celery Background Tasks
+=======================
-Celery is a task queue for Python with batteries included. It used to
-have a Flask integration but it became unnecessary after some
-restructuring of the internals of Celery with Version 3. This guide fills
-in the blanks in how to properly use Celery with Flask but assumes that
-you generally already read the `First Steps with Celery
-`_
-guide in the official Celery documentation.
+If your application has a long running task, such as processing some uploaded
+data or sending email, you don't want to wait for it to finish during a
+request. Instead, use a task queue to send the necessary data to another
+process that will run the task in the background while the request returns
+immediately.
-Installing Celery
------------------
+Celery is a powerful task queue that can be used for simple background tasks
+as well as complex multi-stage programs and schedules. This guide will show you
+how to configure Celery using Flask, but assumes you've already read the
+`First Steps with Celery `_
+guide in the Celery documentation.
-Celery is on the Python Package Index (PyPI), so it can be installed with
-standard Python tools like :command:`pip` or :command:`easy_install`::
+Install
+-------
+
+Celery is a separate Python package. Install it from PyPI using pip::
$ pip install celery
-Configuring Celery
-------------------
+Configure
+---------
The first thing you need is a Celery instance, this is called the celery
application. It serves the same purpose as the :class:`~flask.Flask`
@@ -36,15 +39,18 @@ This is all that is necessary to properly integrate Celery with Flask::
from celery import Celery
def make_celery(app):
- celery = Celery(app.import_name, backend=app.config['CELERY_RESULT_BACKEND'],
- broker=app.config['CELERY_BROKER_URL'])
+ celery = Celery(
+ app.import_name,
+ backend=app.config['CELERY_RESULT_BACKEND'],
+ broker=app.config['CELERY_BROKER_URL']
+ )
celery.conf.update(app.config)
- TaskBase = celery.Task
- class ContextTask(TaskBase):
- abstract = True
+
+ class ContextTask(celery.Task):
def __call__(self, *args, **kwargs):
with app.app_context():
- return TaskBase.__call__(self, *args, **kwargs)
+ return self.run(*args, **kwargs)
+
celery.Task = ContextTask
return celery
@@ -53,11 +59,12 @@ from the application config, updates the rest of the Celery config from
the Flask config and then creates a subclass of the task that wraps the
task execution in an application context.
-Minimal Example
+An example task
---------------
-With what we have above this is the minimal example of using Celery with
-Flask::
+Let's write a task that adds two numbers together and returns the result. We
+configure Celery's broker and backend to use Redis, create a ``celery``
+application using the factor from above, and then use it to define the task. ::
from flask import Flask
@@ -68,26 +75,27 @@ Flask::
)
celery = make_celery(flask_app)
-
@celery.task()
def add_together(a, b):
return a + b
-This task can now be called in the background:
+This task can now be called in the background::
->>> result = add_together.delay(23, 42)
->>> result.wait()
-65
+ result = add_together.delay(23, 42)
+ result.wait() # 65
-Running the Celery Worker
--------------------------
+Run a worker
+------------
-Now if you jumped in and already executed the above code you will be
-disappointed to learn that your ``.wait()`` will never actually return.
-That's because you also need to run celery. You can do that by running
-celery as a worker::
+If you jumped in and already executed the above code you will be
+disappointed to learn that ``.wait()`` will never actually return.
+That's because you also need to run a Celery worker to receive and execute the
+task. ::
$ celery -A your_application.celery worker
The ``your_application`` string has to point to your application's package
-or module that creates the `celery` object.
+or module that creates the ``celery`` object.
+
+Now that the worker is running, ``wait`` will return the result once the task
+is finished.
diff --git a/docs/patterns/deferredcallbacks.rst b/docs/patterns/deferredcallbacks.rst
index 886ae40a..bc20cdd6 100644
--- a/docs/patterns/deferredcallbacks.rst
+++ b/docs/patterns/deferredcallbacks.rst
@@ -3,71 +3,43 @@
Deferred Request Callbacks
==========================
-One of the design principles of Flask is that response objects are created
-and passed down a chain of potential callbacks that can modify them or
-replace them. When the request handling starts, there is no response
-object yet. It is created as necessary either by a view function or by
-some other component in the system.
-
-But what happens if you want to modify the response at a point where the
-response does not exist yet? A common example for that would be a
-before-request function that wants to set a cookie on the response object.
-
-One way is to avoid the situation. Very often that is possible. For
-instance you can try to move that logic into an after-request callback
-instead. Sometimes however moving that code there is just not a very
-pleasant experience or makes code look very awkward.
-
-As an alternative possibility you can attach a bunch of callback functions
-to the :data:`~flask.g` object and call them at the end of the request.
-This way you can defer code execution from anywhere in the application.
-
-
-The Decorator
--------------
-
-The following decorator is the key. It registers a function on a list on
-the :data:`~flask.g` object::
-
- from flask import g
-
- def after_this_request(f):
- if not hasattr(g, 'after_request_callbacks'):
- g.after_request_callbacks = []
- g.after_request_callbacks.append(f)
- return f
-
-
-Calling the Deferred
---------------------
-
-Now you can use the `after_this_request` decorator to mark a function to
-be called at the end of the request. But we still need to call them. For
-this the following function needs to be registered as
-:meth:`~flask.Flask.after_request` callback::
-
- @app.after_request
- def call_after_request_callbacks(response):
- for callback in getattr(g, 'after_request_callbacks', ()):
- callback(response)
- return response
-
-
-A Practical Example
--------------------
+One of the design principles of Flask is that response objects are created and
+passed down a chain of potential callbacks that can modify them or replace
+them. When the request handling starts, there is no response object yet. It is
+created as necessary either by a view function or by some other component in
+the system.
+
+What happens if you want to modify the response at a point where the response
+does not exist yet? A common example for that would be a
+:meth:`~flask.Flask.before_request` callback that wants to set a cookie on the
+response object.
+
+One way is to avoid the situation. Very often that is possible. For instance
+you can try to move that logic into a :meth:`~flask.Flask.after_request`
+callback instead. However, sometimes moving code there makes it more
+more complicated or awkward to reason about.
+
+As an alternative, you can use :func:`~flask.after_this_request` to register
+callbacks that will execute after only the current request. This way you can
+defer code execution from anywhere in the application, based on the current
+request.
At any time during a request, we can register a function to be called at the
-end of the request. For example you can remember the current language of the
-user in a cookie in the before-request function::
+end of the request. For example you can remember the current language of the
+user in a cookie in a :meth:`~flask.Flask.before_request` callback::
- from flask import request
+ from flask import request, after_this_request
@app.before_request
def detect_user_language():
language = request.cookies.get('user_lang')
+
if language is None:
language = guess_language_from_request()
+
+ # when the response exists, set a cookie with the language
@after_this_request
def remember_language(response):
response.set_cookie('user_lang', language)
+
g.language = language
diff --git a/docs/patterns/distribute.rst b/docs/patterns/distribute.rst
index 72cc25d6..0c7c8658 100644
--- a/docs/patterns/distribute.rst
+++ b/docs/patterns/distribute.rst
@@ -88,15 +88,15 @@ support them and they make debugging a lot harder.
Tagging Builds
--------------
-It is useful to distinguish between release and development builds. Add a
-:file:`setup.cfg` file to configure these options.
+It is useful to distinguish between release and development builds. Add a
+:file:`setup.cfg` file to configure these options. ::
[egg_info]
tag_build = .dev
tag_date = 1
[aliases]
- release = egg_info -RDb ''
+ release = egg_info -Db ''
Running ``python setup.py sdist`` will create a development package
with ".dev" and the current date appended: ``flaskr-1.0.dev20160314.tar.gz``.
@@ -174,4 +174,4 @@ the code without having to run ``install`` again after each change.
.. _pip: https://pypi.python.org/pypi/pip
-.. _Setuptools: https://pythonhosted.org/setuptools
+.. _Setuptools: https://pypi.python.org/pypi/setuptools
diff --git a/docs/patterns/errorpages.rst b/docs/patterns/errorpages.rst
index fccd4a6f..1df9c061 100644
--- a/docs/patterns/errorpages.rst
+++ b/docs/patterns/errorpages.rst
@@ -47,37 +47,53 @@ even if the application behaves correctly:
Error Handlers
--------------
-An error handler is a function, just like a view function, but it is
-called when an error happens and is passed that error. The error is most
-likely a :exc:`~werkzeug.exceptions.HTTPException`, but in one case it
-can be a different error: a handler for internal server errors will be
-passed other exception instances as well if they are uncaught.
+An error handler is a function that returns a response when a type of error is
+raised, similar to how a view is a function that returns a response when a
+request URL is matched. It is passed the instance of the error being handled,
+which is most likely a :exc:`~werkzeug.exceptions.HTTPException`. An error
+handler for "500 Internal Server Error" will be passed uncaught exceptions in
+addition to explicit 500 errors.
An error handler is registered with the :meth:`~flask.Flask.errorhandler`
-decorator and the error code of the exception. Keep in mind that Flask
-will *not* set the error code for you, so make sure to also provide the
-HTTP status code when returning a response.
+decorator or the :meth:`~flask.Flask.register_error_handler` method. A handler
+can be registered for a status code, like 404, or for an exception class.
-Please note that if you add an error handler for "500 Internal Server
-Error", Flask will not trigger it if it's running in Debug mode.
+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.
-Here an example implementation for a "404 Page Not Found" exception::
+A handler for "500 Internal Server Error" will not be used when running in
+debug mode. Instead, the interactive debugger will be shown.
+
+Here is an example implementation for a "404 Page Not Found" exception::
from flask import render_template
@app.errorhandler(404)
def page_not_found(e):
+ # note that we set the 404 status explicitly
return render_template('404.html'), 404
+When using the :ref:`application factory pattern `::
+
+ from flask import Flask, render_template
+
+ def page_not_found(e):
+ return render_template('404.html'), 404
+
+ def create_app(config_filename):
+ app = Flask(__name__)
+ app.register_error_handler(404, page_not_found)
+ return app
+
An example template might be this:
.. sourcecode:: html+jinja
- {% extends "layout.html" %}
- {% block title %}Page Not Found{% endblock %}
- {% block body %}
-
Page Not Found
-
What you were looking for is just not there.
-
go somewhere nice
- {% endblock %}
-
+ {% extends "layout.html" %}
+ {% block title %}Page Not Found{% endblock %}
+ {% block body %}
+
Page Not Found
+
What you were looking for is just not there.
+
go somewhere nice
+ {% endblock %}
diff --git a/docs/patterns/favicon.rst b/docs/patterns/favicon.rst
index acdee24b..21ea767f 100644
--- a/docs/patterns/favicon.rst
+++ b/docs/patterns/favicon.rst
@@ -49,5 +49,5 @@ web server's documentation.
See also
--------
-* The `Favicon `_ article on
+* The `Favicon `_ article on
Wikipedia
diff --git a/docs/patterns/fileuploads.rst b/docs/patterns/fileuploads.rst
index 8ab8c033..c7ae14f9 100644
--- a/docs/patterns/fileuploads.rst
+++ b/docs/patterns/fileuploads.rst
@@ -21,7 +21,7 @@ specific upload folder and displays a file to the user. Let's look at the
bootstrapping code for our application::
import os
- from flask import Flask, request, redirect, url_for
+ from flask import Flask, flash, request, redirect, url_for
from werkzeug.utils import secure_filename
UPLOAD_FOLDER = '/path/to/the/uploads'
@@ -58,22 +58,22 @@ the file and redirects the user to the URL for the uploaded file::
return redirect(request.url)
file = request.files['file']
# if user does not select file, browser also
- # submit a empty part without filename
+ # submit an empty part without filename
if file.filename == '':
flash('No selected file')
return redirect(request.url)
if file and allowed_file(file.filename):
filename = secure_filename(file.filename)
file.save(os.path.join(app.config['UPLOAD_FOLDER'], filename))
- return redirect(url_for('uploaded_file',
+ return redirect(url_for('upload_file',
filename=filename))
return '''
Upload new File
Upload new File
'''
@@ -149,8 +149,8 @@ config key::
app = Flask(__name__)
app.config['MAX_CONTENT_LENGTH'] = 16 * 1024 * 1024
-The code above will limited the maximum allowed payload to 16 megabytes.
-If a larger file is transmitted, Flask will raise an
+The code above will limit the maximum allowed payload to 16 megabytes.
+If a larger file is transmitted, Flask will raise a
:exc:`~werkzeug.exceptions.RequestEntityTooLarge` exception.
This feature was added in Flask 0.6 but can be achieved in older versions
@@ -181,4 +181,4 @@ applications dealing with uploads, there is also a Flask extension called
blacklisting of extensions and more.
.. _jQuery: https://jquery.com/
-.. _Flask-Uploads: http://pythonhosted.org/Flask-Uploads/
+.. _Flask-Uploads: https://pythonhosted.org/Flask-Uploads/
diff --git a/docs/patterns/flashing.rst b/docs/patterns/flashing.rst
index 7efd1446..a61c719f 100644
--- a/docs/patterns/flashing.rst
+++ b/docs/patterns/flashing.rst
@@ -22,7 +22,7 @@ So here is a full example::
request, url_for
app = Flask(__name__)
- app.secret_key = 'some_secret'
+ app.secret_key = b'_5#y2L"F4Q8z\n\xec]/'
@app.route('/')
def index():
diff --git a/docs/patterns/packages.rst b/docs/patterns/packages.rst
index 1cd77974..6b0ee7ad 100644
--- a/docs/patterns/packages.rst
+++ b/docs/patterns/packages.rst
@@ -17,6 +17,10 @@ this::
login.html
...
+If you find yourself stuck on something, feel free
+to take a look at the source code for this example.
+You'll find `the full src for this example here`_.
+
Simple Packages
---------------
@@ -61,10 +65,10 @@ that tells Flask where to find the application instance::
export FLASK_APP=yourapplication
If you are outside of the project directory make sure to provide the exact
-path to your application directory. Similiarly you can turn on "debug
-mode" with this environment variable::
+path to your application directory. Similarly you can turn on the
+development features like this::
- export FLASK_DEBUG=true
+ export FLASK_ENV=development
In order to install and run the application you need to issue the following
commands::
@@ -130,6 +134,7 @@ You should then end up with something like that::
.. _working-with-modules:
+.. _the full src for this example here: https://github.com/pallets/flask/tree/master/examples/patterns/largerapp
Working with Blueprints
-----------------------
diff --git a/docs/patterns/sqlalchemy.rst b/docs/patterns/sqlalchemy.rst
index 40e048e0..8785a6e2 100644
--- a/docs/patterns/sqlalchemy.rst
+++ b/docs/patterns/sqlalchemy.rst
@@ -22,7 +22,7 @@ if you want to get started quickly.
You can download `Flask-SQLAlchemy`_ from `PyPI
`_.
-.. _Flask-SQLAlchemy: http://pythonhosted.org/Flask-SQLAlchemy/
+.. _Flask-SQLAlchemy: http://flask-sqlalchemy.pocoo.org/
Declarative
@@ -108,9 +108,9 @@ Querying is simple as well:
>>> User.query.filter(User.name == 'admin').first()
-.. _SQLAlchemy: http://www.sqlalchemy.org/
+.. _SQLAlchemy: https://www.sqlalchemy.org/
.. _declarative:
- http://docs.sqlalchemy.org/en/latest/orm/extensions/declarative/
+ https://docs.sqlalchemy.org/en/latest/orm/extensions/declarative/
Manual Object Relational Mapping
--------------------------------
@@ -135,7 +135,7 @@ Here is an example :file:`database.py` module for your application::
def init_db():
metadata.create_all(bind=engine)
-As for the declarative approach you need to close the session after
+As in the declarative approach, you need to close the session after
each request or application context shutdown. Put this into your
application module::
@@ -215,4 +215,4 @@ You can also pass strings of SQL statements to the
(1, u'admin', u'admin@localhost')
For more information about SQLAlchemy, head over to the
-`website `_.
+`website `_.
diff --git a/docs/patterns/sqlite3.rst b/docs/patterns/sqlite3.rst
index 66a7c4c4..eecaaae8 100644
--- a/docs/patterns/sqlite3.rst
+++ b/docs/patterns/sqlite3.rst
@@ -3,8 +3,8 @@
Using SQLite 3 with Flask
=========================
-In Flask you can easily implement the opening of database connections on
-demand and closing them when the context dies (usually at the end of the
+In Flask you can easily implement the opening of database connections on
+demand and closing them when the context dies (usually at the end of the
request).
Here is a simple example of how you can use SQLite 3 with Flask::
@@ -67,11 +67,11 @@ the application context by hand::
Easy Querying
-------------
-Now in each request handling function you can access `g.db` to get the
+Now in each request handling function you can access `get_db()` to get the
current open database connection. To simplify working with SQLite, a
row factory function is useful. It is executed for every result returned
from the database to convert the result. For instance, in order to get
-dictionaries instead of tuples, this could be inserted into the ``get_db``
+dictionaries instead of tuples, this could be inserted into the ``get_db``
function we created above::
def make_dicts(cursor, row):
@@ -102,15 +102,15 @@ This would use Row objects rather than dicts to return the results of queries. T
Additionally, it is a good idea to provide a query function that combines
getting the cursor, executing and fetching the results::
-
+
def query_db(query, args=(), one=False):
cur = get_db().execute(query, args)
rv = cur.fetchall()
cur.close()
return (rv[0] if rv else None) if one else rv
-This handy little function, in combination with a row factory, makes
-working with the database much more pleasant than it is by just using the
+This handy little function, in combination with a row factory, makes
+working with the database much more pleasant than it is by just using the
raw cursor and connection objects.
Here is how you can use it::
@@ -131,7 +131,7 @@ To pass variable parts to the SQL statement, use a question mark in the
statement and pass in the arguments as a list. Never directly add them to
the SQL statement with string formatting because this makes it possible
to attack the application using `SQL Injections
-`_.
+`_.
Initial Schemas
---------------
diff --git a/docs/patterns/wtforms.rst b/docs/patterns/wtforms.rst
index 2649cad6..0e53de17 100644
--- a/docs/patterns/wtforms.rst
+++ b/docs/patterns/wtforms.rst
@@ -19,7 +19,7 @@ forms.
fun. You can get it from `PyPI
`_.
-.. _Flask-WTF: http://pythonhosted.org/Flask-WTF/
+.. _Flask-WTF: https://flask-wtf.readthedocs.io/en/stable/
The Forms
---------
diff --git a/docs/python3.rst b/docs/python3.rst
deleted file mode 100644
index a7a4f165..00000000
--- a/docs/python3.rst
+++ /dev/null
@@ -1,23 +0,0 @@
-.. _python3-support:
-
-Python 3 Support
-================
-
-Flask, its dependencies, and most Flask extensions support Python 3.
-You should start using Python 3 for your next project,
-but there are a few things to be aware of.
-
-You need to use Python 3.3 or higher. 3.2 and older are *not* supported.
-
-You should use the latest versions of all Flask-related packages.
-Flask 0.10 and Werkzeug 0.9 were the first versions to introduce Python 3 support.
-
-Python 3 changed how unicode and bytes are handled, which complicates how low
-level code handles HTTP data. This mainly affects WSGI middleware interacting
-with the WSGI ``environ`` data. Werkzeug wraps that information in high-level
-helpers, so encoding issues should not affect you.
-
-The majority of the upgrade work is in the lower-level libraries like
-Flask and Werkzeug, not the high-level application code.
-For example, all of the examples in the Flask repository work on both Python 2 and 3
-and did not require a single line of code changed.
diff --git a/docs/quickstart.rst b/docs/quickstart.rst
index b444e080..334d7dc4 100644
--- a/docs/quickstart.rst
+++ b/docs/quickstart.rst
@@ -50,7 +50,14 @@ to tell your terminal the application to work with by exporting the
$ flask run
* Running on http://127.0.0.1:5000/
-If you are on Windows you need to use ``set`` instead of ``export``.
+If you are on Windows, the environment variable syntax depends on command line
+interpreter. On Command Prompt::
+
+ C:\path\to\app>set FLASK_APP=hello.py
+
+And on PowerShell::
+
+ PS C:\path\to\app> $env:FLASK_APP = "hello.py"
Alternatively you can use :command:`python -m flask`::
@@ -102,9 +109,9 @@ docs to see the alternative method for running a server.
Invalid Import Name
```````````````````
-The ``FLASK_APP`` environment variable is the name of the module to import at
-:command:`flask run`. In case that module is incorrectly named you will get an
-import error upon start (or if debug is enabled when you navigate to the
+The ``FLASK_APP`` environment variable is the name of the module to import at
+:command:`flask run`. In case that module is incorrectly named you will get an
+import error upon start (or if debug is enabled when you navigate to the
application). It will tell you what it tried to import and why it failed.
The most common reason is a typo or because you did not actually create an
@@ -123,13 +130,14 @@ That is not very nice and Flask can do better. If you enable debug
support the server will reload itself on code changes, and it will also
provide you with a helpful debugger if things go wrong.
-To enable debug mode you can export the ``FLASK_DEBUG`` environment variable
+To enable all development features (including debug mode) you can export
+the ``FLASK_ENV`` environment variable and set it to ``development``
before running the server::
- $ export FLASK_DEBUG=1
+ $ export FLASK_ENV=development
$ flask run
-(On Windows you need to use ``set`` instead of ``export``).
+(On Windows you need to use ``set`` instead of ``export``.)
This does the following things:
@@ -137,6 +145,9 @@ This does the following things:
2. it activates the automatic reloader
3. it enables the debug mode on the Flask application.
+You can also control debug mode separately from the environment by
+exporting ``FLASK_DEBUG=1``.
+
There are more parameters that are explained in the :ref:`server` docs.
.. admonition:: Attention
@@ -153,20 +164,22 @@ Screenshot of the debugger in action:
:class: screenshot
:alt: screenshot of debugger in action
+More information on using the debugger can be found in the `Werkzeug
+documentation`_.
+
+.. _Werkzeug documentation: http://werkzeug.pocoo.org/docs/debug/#using-the-debugger
+
Have another debugger in mind? See :ref:`working-with-debuggers`.
Routing
-------
-Modern web applications have beautiful URLs. This helps people remember
-the URLs, which is especially handy for applications that are used from
-mobile devices with slower network connections. If the user can directly
-go to the desired page without having to hit the index page it is more
-likely they will like the page and come back next time.
+Modern web applications use meaningful URLs to help users. Users are more
+likely to like a page and come back if the page uses a meaningful URL they can
+remember and use to directly visit a page.
-As you have seen above, the :meth:`~flask.Flask.route` decorator is used to
-bind a function to a URL. Here are some basic examples::
+Use the :meth:`~flask.Flask.route` decorator to bind a function to a URL. ::
@app.route('/')
def index():
@@ -176,16 +189,16 @@ bind a function to a URL. Here are some basic examples::
def hello():
return 'Hello, World'
-But there is more to it! You can make certain parts of the URL dynamic and
-attach multiple rules to a function.
+You can do more! You can make parts of the URL dynamic and attach multiple
+rules to a function.
Variable Rules
``````````````
-To add variable parts to a URL you can mark these special sections as
-````. Such a part is then passed as a keyword argument to your
-function. Optionally a converter can be used by specifying a rule with
-````. Here are some nice examples::
+You can add variable sections to a URL by marking sections with
+````. Your function then receives the ````
+as a keyword argument. Optionally, you can use a converter to specify the type
+of the argument like ````. ::
@app.route('/user/')
def show_user_profile(username):
@@ -197,177 +210,124 @@ function. Optionally a converter can be used by specifying a rule with
# show the post with the given id, the id is an integer
return 'Post %d' % post_id
-The following converters exist:
-
-=========== ===============================================
-`string` accepts any text without a slash (the default)
-`int` accepts integers
-`float` like ``int`` but for floating point values
-`path` like the default but also accepts slashes
-`any` matches one of the items provided
-`uuid` accepts UUID strings
-=========== ===============================================
+ @app.route('/path/')
+ def show_subpath(subpath):
+ # show the subpath after /path/
+ return 'Subpath %s' % subpath
-.. admonition:: Unique URLs / Redirection Behavior
+Converter types:
- Flask's URL rules are based on Werkzeug's routing module. The idea
- behind that module is to ensure beautiful and unique URLs based on
- precedents laid down by Apache and earlier HTTP servers.
+========== ==========================================
+``string`` (default) accepts any text without a slash
+``int`` accepts positive integers
+``float`` accepts positive floating point values
+``path`` like ``string`` but also accepts slashes
+``uuid`` accepts UUID strings
+========== ==========================================
- Take these two rules::
+Unique URLs / Redirection Behavior
+``````````````````````````````````
- @app.route('/projects/')
- def projects():
- return 'The project page'
+Take these two rules::
- @app.route('/about')
- def about():
- return 'The about page'
+ @app.route('/projects/')
+ def projects():
+ return 'The project page'
- Though they look rather similar, they differ in their use of the trailing
- slash in the URL *definition*. In the first case, the canonical URL for the
- ``projects`` endpoint has a trailing slash. In that sense, it is similar to
- a folder on a filesystem. Accessing it without a trailing slash will cause
- Flask to redirect to the canonical URL with the trailing slash.
+ @app.route('/about')
+ def about():
+ return 'The about page'
- In the second case, however, the URL is defined without a trailing slash,
- rather like the pathname of a file on UNIX-like systems. Accessing the URL
- with a trailing slash will produce a 404 "Not Found" error.
+Though they look similar, they differ in their use of the trailing slash in
+the URL. In the first case, the canonical URL for the ``projects`` endpoint
+uses a trailing slash. It's similar to a folder in a file system; if you
+access the URL without a trailing slash, Flask redirects you to the
+canonical URL with the trailing slash.
- This behavior allows relative URLs to continue working even if the trailing
- slash is omitted, consistent with how Apache and other servers work. Also,
- the URLs will stay unique, which helps search engines avoid indexing the
- same page twice.
+In the second case, however, the URL definition lacks a trailing slash,
+like the pathname of a file on UNIX-like systems. Accessing the URL with a
+trailing slash produces a 404 “Not Found” error.
+This behavior allows relative URLs to continue working even if the trailing
+slash is omitted, consistent with how Apache and other servers work. Also,
+the URLs will stay unique, which helps search engines avoid indexing the
+same page twice.
.. _url-building:
URL Building
````````````
-If it can match URLs, can Flask also generate them? Of course it can. To
-build a URL to a specific function you can use the :func:`~flask.url_for`
-function. It accepts the name of the function as first argument and a number
-of keyword arguments, each corresponding to the variable part of the URL rule.
-Unknown variable parts are appended to the URL as query parameters. Here are
-some examples::
-
- >>> from flask import Flask, url_for
- >>> app = Flask(__name__)
- >>> @app.route('/')
- ... def index(): pass
- ...
- >>> @app.route('/login')
- ... def login(): pass
- ...
- >>> @app.route('/user/')
- ... def profile(username): pass
- ...
- >>> with app.test_request_context():
- ... print url_for('index')
- ... print url_for('login')
- ... print url_for('login', next='/')
- ... print url_for('profile', username='John Doe')
- ...
- /
- /login
- /login?next=/
- /user/John%20Doe
-
-(This also uses the :meth:`~flask.Flask.test_request_context` method, explained
-below. It tells Flask to behave as though it is handling a request, even
-though we are interacting with it through a Python shell. Have a look at the
-explanation below. :ref:`context-locals`).
+To build a URL to a specific function, use the :func:`~flask.url_for` function.
+It accepts the name of the function as its first argument and any number of
+keyword arguments, each corresponding to a variable part of the URL rule.
+Unknown variable parts are appended to the URL as query parameters.
Why would you want to build URLs using the URL reversing function
:func:`~flask.url_for` instead of hard-coding them into your templates?
-There are three good reasons for this:
-1. Reversing is often more descriptive than hard-coding the URLs. More
- importantly, it allows you to change URLs in one go, without having to
- remember to change URLs all over the place.
-2. URL building will handle escaping of special characters and Unicode
- data transparently for you, so you don't have to deal with them.
-3. If your application is placed outside the URL root - say, in
- ``/myapplication`` instead of ``/`` - :func:`~flask.url_for` will handle
- that properly for you.
+1. Reversing is often more descriptive than hard-coding the URLs.
+2. You can change your URLs in one go instead of needing to remember to
+ manually change hard-coded URLs.
+3. URL building handles escaping of special characters and Unicode data
+ transparently.
+4. If your application is placed outside the URL root, for example, in
+ ``/myapplication`` instead of ``/``, :func:`~flask.url_for` properly
+ handles that for you.
+
+For example, here we use the :meth:`~flask.Flask.test_request_context` method
+to try out :func:`~flask.url_for`. :meth:`~flask.Flask.test_request_context`
+tells Flask to behave as though it's handling a request even while we use a
+Python shell. See :ref:`context-locals`. ::
+
+ from flask import Flask, url_for
+
+ app = Flask(__name__)
+
+ @app.route('/')
+ def index():
+ return 'index'
+
+ @app.route('/login')
+ def login():
+ return 'login'
+ @app.route('/user/')
+ def profile(username):
+ return '{}'s profile'.format(username)
+
+ with app.test_request_context():
+ print(url_for('index'))
+ print(url_for('login'))
+ print(url_for('login', next='/'))
+ print(url_for('profile', username='John Doe'))
+
+ /
+ /login
+ /login?next=/
+ /user/John%20Doe
HTTP Methods
````````````
-HTTP (the protocol web applications are speaking) knows different methods for
-accessing URLs. By default, a route only answers to ``GET`` requests, but that
-can be changed by providing the ``methods`` argument to the
-:meth:`~flask.Flask.route` decorator. Here are some examples::
-
- from flask import request
+Web applications use different HTTP methods when accessing URLs. You should
+familiarize yourself with the HTTP methods as you work with Flask. By default,
+a route only answers to ``GET`` requests. You can use the ``methods`` argument
+of the :meth:`~flask.Flask.route` decorator to handle different HTTP methods.
+::
@app.route('/login', methods=['GET', 'POST'])
def login():
if request.method == 'POST':
- do_the_login()
+ return do_the_login()
else:
- show_the_login_form()
-
-If ``GET`` is present, ``HEAD`` will be added automatically for you. You
-don't have to deal with that. It will also make sure that ``HEAD`` requests
-are handled as the `HTTP RFC`_ (the document describing the HTTP
-protocol) demands, so you can completely ignore that part of the HTTP
-specification. Likewise, as of Flask 0.6, ``OPTIONS`` is implemented for you
-automatically as well.
-
-You have no idea what an HTTP method is? Worry not, here is a quick
-introduction to HTTP methods and why they matter:
-
-The HTTP method (also often called "the verb") tells the server what the
-client wants to *do* with the requested page. The following methods are
-very common:
-
-``GET``
- The browser tells the server to just *get* the information stored on
- that page and send it. This is probably the most common method.
-
-``HEAD``
- The browser tells the server to get the information, but it is only
- interested in the *headers*, not the content of the page. An
- application is supposed to handle that as if a ``GET`` request was
- received but to not deliver the actual content. In Flask you don't
- have to deal with that at all, the underlying Werkzeug library handles
- that for you.
-
-``POST``
- The browser tells the server that it wants to *post* some new
- information to that URL and that the server must ensure the data is
- stored and only stored once. This is how HTML forms usually
- transmit data to the server.
-
-``PUT``
- Similar to ``POST`` but the server might trigger the store procedure
- multiple times by overwriting the old values more than once. Now you
- might be asking why this is useful, but there are some good reasons
- to do it this way. Consider that the connection is lost during
- transmission: in this situation a system between the browser and the
- server might receive the request safely a second time without breaking
- things. With ``POST`` that would not be possible because it must only
- be triggered once.
-
-``DELETE``
- Remove the information at the given location.
-
-``OPTIONS``
- Provides a quick way for a client to figure out which methods are
- supported by this URL. Starting with Flask 0.6, this is implemented
- for you automatically.
-
-Now the interesting part is that in HTML4 and XHTML1, the only methods a
-form can submit to the server are ``GET`` and ``POST``. But with JavaScript
-and future HTML standards you can use the other methods as well. Furthermore
-HTTP has become quite popular lately and browsers are no longer the only
-clients that are using HTTP. For instance, many revision control systems
-use it.
-
-.. _HTTP RFC: http://www.ietf.org/rfc/rfc2068.txt
+ return show_the_login_form()
+
+If ``GET`` is present, Flask automatically adds support for the ``HEAD`` method
+and handles ``HEAD`` requests according to the the `HTTP RFC`_. Likewise,
+``OPTIONS`` is automatically implemented for you.
+
+.. _HTTP RFC: https://www.ietf.org/rfc/rfc2068.txt
Static Files
------------
@@ -538,16 +498,16 @@ The Request Object
``````````````````
The request object is documented in the API section and we will not cover
-it here in detail (see :class:`~flask.request`). Here is a broad overview of
+it here in detail (see :class:`~flask.Request`). Here is a broad overview of
some of the most common operations. First of all you have to import it from
the ``flask`` module::
from flask import request
The current request method is available by using the
-:attr:`~flask.request.method` attribute. To access form data (data
+:attr:`~flask.Request.method` attribute. To access form data (data
transmitted in a ``POST`` or ``PUT`` request) you can use the
-:attr:`~flask.request.form` attribute. Here is a full example of the two
+:attr:`~flask.Request.form` attribute. Here is a full example of the two
attributes mentioned above::
@app.route('/login', methods=['POST', 'GET'])
@@ -570,7 +530,7 @@ error page is shown instead. So for many situations you don't have to
deal with that problem.
To access parameters submitted in the URL (``?key=value``) you can use the
-:attr:`~flask.request.args` attribute::
+:attr:`~flask.Request.args` attribute::
searchword = request.args.get('key', '')
@@ -579,7 +539,7 @@ We recommend accessing URL parameters with `get` or by catching the
bad request page in that case is not user friendly.
For a full list of methods and attributes of the request object, head over
-to the :class:`~flask.request` documentation.
+to the :class:`~flask.Request` documentation.
File Uploads
@@ -768,6 +728,9 @@ sessions work::
app = Flask(__name__)
+ # Set the secret key to some random bytes. Keep this really secret!
+ app.secret_key = b'_5#y2L"F4Q8z\n\xec]/'
+
@app.route('/')
def index():
if 'username' in session:
@@ -792,24 +755,18 @@ sessions work::
session.pop('username', None)
return redirect(url_for('index'))
- # set the secret key. keep this really secret:
- app.secret_key = 'A0Zr98j/3yX R~XHH!jmN]LWX/,?RT'
-
The :func:`~flask.escape` mentioned here does escaping for you if you are
not using the template engine (as in this example).
.. admonition:: How to generate good secret keys
- The problem with random is that it's hard to judge what is truly random. And
- a secret key should be as random as possible. Your operating system
- has ways to generate pretty random stuff based on a cryptographic
- random generator which can be used to get such a key::
-
- >>> import os
- >>> os.urandom(24)
- '\xfd{H\xe5<\x95\xf9\xe3\x96.5\xd1\x01O`_.
+`_.
Flask configures Jinja2 to automatically escape all values unless
explicitly told otherwise. This should rule out all XSS problems caused
@@ -38,7 +38,7 @@ either double or single quotes when using Jinja expressions in them:
.. sourcecode:: html+jinja
- the text
+
Why is this necessary? Because if you would not be doing that, an
attacker could easily inject custom JavaScript handlers. For example an
@@ -46,15 +46,26 @@ attacker could inject this piece of HTML+JavaScript:
.. sourcecode:: html
- onmouseover=alert(document.cookie)
+ onmouseover=alert(document.cookie)
-When the user would then move with the mouse over the link, the cookie
+When the user would then move with the mouse over the input, the cookie
would be presented to the user in an alert window. But instead of showing
the cookie to the user, a good attacker might also execute any other
JavaScript code. In combination with CSS injections the attacker might
even make the element fill out the entire page so that the user would
just have to have the mouse anywhere on the page to trigger the attack.
+There is one class of XSS issues that Jinja's escaping does not protect
+against. The ``a`` tag's ``href`` attribute can contain a `javascript:` URI,
+which the browser will execute when clicked if not secured properly.
+
+.. sourcecode:: html
+
+ click here
+ click here
+
+To prevent this, you'll need to set the :ref:`security-csp` response header.
+
Cross-Site Request Forgery (CSRF)
---------------------------------
@@ -104,3 +115,146 @@ vulnerabilities
`_, so
this behavior was changed and :func:`~flask.jsonify` now supports serializing
arrays.
+
+Security Headers
+----------------
+
+Browsers recognize various response headers in order to control security. We
+recommend reviewing each of the headers below for use in your application.
+The `Flask-Talisman`_ extension can be used to manage HTTPS and the security
+headers for you.
+
+.. _Flask-Talisman: https://github.com/GoogleCloudPlatform/flask-talisman
+
+HTTP Strict Transport Security (HSTS)
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Tells the browser to convert all HTTP requests to HTTPS, preventing
+man-in-the-middle (MITM) attacks. ::
+
+ response.headers['Strict-Transport-Security'] = 'max-age=31536000; includeSubDomains'
+
+- https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Strict-Transport-Security
+
+.. _security-csp:
+
+Content Security Policy (CSP)
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Tell the browser where it can load various types of resource from. This header
+should be used whenever possible, but requires some work to define the correct
+policy for your site. A very strict policy would be::
+
+ response.headers['Content-Security-Policy'] = "default-src 'self'"
+
+- https://csp.withgoogle.com/docs/index.html
+- https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy
+
+X-Content-Type-Options
+~~~~~~~~~~~~~~~~~~~~~~
+
+Forces the browser to honor the response content type instead of trying to
+detect it, which can be abused to generate a cross-site scripting (XSS)
+attack. ::
+
+ response.headers['X-Content-Type-Options'] = 'nosniff'
+
+- https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Content-Type-Options
+
+X-Frame-Options
+~~~~~~~~~~~~~~~
+
+Prevents external sites from embedding your site in an ``iframe``. This
+prevents a class of attacks where clicks in the outer frame can be translated
+invisibly to clicks on your page's elements. This is also known as
+"clickjacking". ::
+
+ response.headers['X-Frame-Options'] = 'SAMEORIGIN'
+
+- https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Frame-Options
+
+X-XSS-Protection
+~~~~~~~~~~~~~~~~
+
+The browser will try to prevent reflected XSS attacks by not loading the page
+if the request contains something that looks like JavaScript and the response
+contains the same data. ::
+
+ response.headers['X-XSS-Protection'] = '1; mode=block'
+
+- https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-XSS-Protection
+
+
+.. _security-cookie:
+
+Set-Cookie options
+~~~~~~~~~~~~~~~~~~
+
+These options can be added to a ``Set-Cookie`` header to improve their
+security. Flask has configuration options to set these on the session cookie.
+They can be set on other cookies too.
+
+- ``Secure`` limits cookies to HTTPS traffic only.
+- ``HttpOnly`` protects the contents of cookies from being read with
+ JavaScript.
+- ``SameSite`` restricts how cookies are sent with requests from
+ external sites. Can be set to ``'Lax'`` (recommended) or ``'Strict'``.
+ ``Lax`` prevents sending cookies with CSRF-prone requests from
+ external sites, such as submitting a form. ``Strict`` prevents sending
+ cookies with all external requests, including following regular links.
+
+::
+
+ app.config.update(
+ SESSION_COOKIE_SECURE=True,
+ SESSION_COOKIE_HTTPONLY=True,
+ SESSION_COOKIE_SAMESITE='Lax',
+ )
+
+ response.set_cookie('username', 'flask', secure=True, httponly=True, samesite='Lax')
+
+Specifying ``Expires`` or ``Max-Age`` options, will remove the cookie after
+the given time, or the current time plus the age, respectively. If neither
+option is set, the cookie will be removed when the browser is closed. ::
+
+ # cookie expires after 10 minutes
+ response.set_cookie('snakes', '3', max_age=600)
+
+For the session cookie, if :attr:`session.permanent `
+is set, then :data:`PERMANENT_SESSION_LIFETIME` is used to set the expiration.
+Flask's default cookie implementation validates that the cryptographic
+signature is not older than this value. Lowering this value may help mitigate
+replay attacks, where intercepted cookies can be sent at a later time. ::
+
+ app.config.update(
+ PERMANENT_SESSION_LIFETIME=600
+ )
+
+ @app.route('/login', methods=['POST'])
+ def login():
+ ...
+ session.clear()
+ session['user_id'] = user.id
+ session.permanent = True
+ ...
+
+Use :class:`itsdangerous.TimedSerializer` to sign and validate other cookie
+values (or any values that need secure signatures).
+
+- https://developer.mozilla.org/en-US/docs/Web/HTTP/Cookies
+- https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie
+
+.. _samesite_support: https://caniuse.com/#feat=same-site-cookie-attribute
+
+
+HTTP Public Key Pinning (HPKP)
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+This tells the browser to authenticate with the server using only the specific
+certificate key to prevent MITM attacks.
+
+.. warning::
+ Be careful when enabling this, as it is very difficult to undo if you set up
+ or upgrade your key incorrectly.
+
+- https://developer.mozilla.org/en-US/docs/Web/HTTP/Public_Key_Pinning
diff --git a/docs/server.rst b/docs/server.rst
index f8332ebf..db431a6c 100644
--- a/docs/server.rst
+++ b/docs/server.rst
@@ -12,23 +12,33 @@ but you can also continue using the :meth:`Flask.run` method.
Command Line
------------
-The :command:`flask` command line script (:ref:`cli`) is strongly recommended for
-development because it provides a superior reload experience due to how it
-loads the application. The basic usage is like this::
+The :command:`flask` command line script (:ref:`cli`) is strongly
+recommended for development because it provides a superior reload
+experience due to how it loads the application. The basic usage is like
+this::
$ export FLASK_APP=my_application
- $ export FLASK_DEBUG=1
+ $ export FLASK_ENV=development
$ flask run
-This will enable the debugger, the reloader and then start the server on
+This enables the development environment, including the interactive
+debugger and reloader, and then starts the server on
*http://localhost:5000/*.
The individual features of the server can be controlled by passing more
-arguments to the ``run`` option. For instance the reloader can be
+arguments to the ``run`` option. For instance the reloader can be
disabled::
$ flask run --no-reload
+.. note::
+
+ Prior to Flask 1.0 the :envvar:`FLASK_ENV` environment variable was
+ not supported and you needed to enable debug mode by exporting
+ ``FLASK_DEBUG=1``. This can still be used to control debug mode, but
+ you should prefer setting the development environment as shown
+ above.
+
In Code
-------
diff --git a/docs/signals.rst b/docs/signals.rst
index 2426e920..40041491 100644
--- a/docs/signals.rst
+++ b/docs/signals.rst
@@ -27,7 +27,7 @@ executed in undefined order and do not modify any data.
The big advantage of signals over handlers is that you can safely
subscribe to them for just a split second. These temporary
-subscriptions are helpful for unittesting for example. Say you want to
+subscriptions are helpful for unit testing for example. Say you want to
know what templates were rendered as part of a request: signals allow you
to do exactly that.
@@ -45,7 +45,7 @@ signal. When you subscribe to a signal, be sure to also provide a sender
unless you really want to listen for signals from all applications. This is
especially true if you are developing an extension.
-For example, here is a helper context manager that can be used in a unittest
+For example, here is a helper context manager that can be used in a unit test
to determine which templates were rendered and what variables were passed
to the template::
diff --git a/docs/styleguide.rst b/docs/styleguide.rst
index e03e4ef5..390d5668 100644
--- a/docs/styleguide.rst
+++ b/docs/styleguide.rst
@@ -167,7 +167,7 @@ Docstring conventions:
"""
Module header:
- The module header consists of an utf-8 encoding declaration (if non
+ The module header consists of a utf-8 encoding declaration (if non
ASCII letters are used, but it is recommended all the time) and a
standard docstring::
diff --git a/docs/templating.rst b/docs/templating.rst
index 9ba2223a..c0af6639 100644
--- a/docs/templating.rst
+++ b/docs/templating.rst
@@ -1,3 +1,5 @@
+.. _templates:
+
Templates
=========
diff --git a/docs/testing.rst b/docs/testing.rst
index 0737936e..79856341 100644
--- a/docs/testing.rst
+++ b/docs/testing.rst
@@ -5,23 +5,30 @@ Testing Flask Applications
**Something that is untested is broken.**
-The origin of this quote is unknown and while it is not entirely correct, it is also
-not far from the truth. Untested applications make it hard to
+The origin of this quote is unknown and while it is not entirely correct, it
+is also not far from the truth. Untested applications make it hard to
improve existing code and developers of untested applications tend to
become pretty paranoid. If an application has automated tests, you can
safely make changes and instantly know if anything breaks.
Flask provides a way to test your application by exposing the Werkzeug
test :class:`~werkzeug.test.Client` and handling the context locals for you.
-You can then use that with your favourite testing solution. In this documentation
-we will use the :mod:`unittest` package that comes pre-installed with Python.
+You can then use that with your favourite testing solution.
+
+In this documentation we will use the `pytest`_ package as the base
+framework for our tests. You can install it with ``pip``, like so::
+
+ pip install pytest
+
+.. _pytest:
+ https://pytest.org
The Application
---------------
First, we need an application to test; we will use the application from
the :ref:`tutorial`. If you don't have that application yet, get the
-sources from `the examples`_.
+source code from `the examples`_.
.. _the examples:
https://github.com/pallets/flask/tree/master/examples/flaskr/
@@ -29,90 +36,91 @@ sources from `the examples`_.
The Testing Skeleton
--------------------
-In order to test the application, we add a second module
-(:file:`flaskr_tests.py`) and create a unittest skeleton there::
+We begin by adding a tests directory under the application root. Then
+create a Python file to store our tests (:file:`test_flaskr.py`). When we
+format the filename like ``test_*.py``, it will be auto-discoverable by
+pytest.
+
+Next, we create a `pytest fixture`_ called
+:func:`client` that configures
+the application for testing and initializes a new database.::
import os
- import flaskr
- import unittest
import tempfile
- class FlaskrTestCase(unittest.TestCase):
+ import pytest
- def setUp(self):
- self.db_fd, flaskr.app.config['DATABASE'] = tempfile.mkstemp()
- flaskr.app.config['TESTING'] = True
- self.app = flaskr.app.test_client()
- with flaskr.app.app_context():
- flaskr.init_db()
+ from flaskr import flaskr
- def tearDown(self):
- os.close(self.db_fd)
- os.unlink(flaskr.app.config['DATABASE'])
- if __name__ == '__main__':
- unittest.main()
+ @pytest.fixture
+ def client():
+ db_fd, flaskr.app.config['DATABASE'] = tempfile.mkstemp()
+ flaskr.app.config['TESTING'] = True
+ client = flaskr.app.test_client()
+
+ with flaskr.app.app_context():
+ flaskr.init_db()
+
+ yield client
-The code in the :meth:`~unittest.TestCase.setUp` method creates a new test
-client and initializes a new database. This function is called before
-each individual test function is run. To delete the database after the
-test, we close the file and remove it from the filesystem in the
-:meth:`~unittest.TestCase.tearDown` method. Additionally during setup the
-``TESTING`` config flag is activated. What it does is disable the error
-catching during request handling so that you get better error reports when
-performing test requests against the application.
+ os.close(db_fd)
+ os.unlink(flaskr.app.config['DATABASE'])
-This test client will give us a simple interface to the application. We can
-trigger test requests to the application, and the client will also keep track
-of cookies for us.
+This client fixture will be called by each individual test. It gives us a
+simple interface to the application, where we can trigger test requests to the
+application. The client will also keep track of cookies for us.
-Because SQLite3 is filesystem-based we can easily use the tempfile module
+During setup, the ``TESTING`` config flag is activated. What
+this does is disable error catching during request handling, so that
+you get better error reports when performing test requests against the
+application.
+
+Because SQLite3 is filesystem-based, we can easily use the :mod:`tempfile` module
to create a temporary database and initialize it. The
:func:`~tempfile.mkstemp` function does two things for us: it returns a
low-level file handle and a random file name, the latter we use as
database name. We just have to keep the `db_fd` around so that we can use
the :func:`os.close` function to close the file.
+To delete the database after the test, the fixture closes the file and removes
+it from the filesystem.
+
If we now run the test suite, we should see the following output::
- $ python flaskr_tests.py
+ $ pytest
- ----------------------------------------------------------------------
- Ran 0 tests in 0.000s
+ ================ test session starts ================
+ rootdir: ./flask/examples/flaskr, inifile: setup.cfg
+ collected 0 items
- OK
+ =========== no tests ran in 0.07 seconds ============
-Even though it did not run any actual tests, we already know that our flaskr
+Even though it did not run any actual tests, we already know that our ``flaskr``
application is syntactically valid, otherwise the import would have died
with an exception.
+.. _pytest fixture:
+ https://docs.pytest.org/en/latest/fixture.html
+
The First Test
--------------
Now it's time to start testing the functionality of the application.
Let's check that the application shows "No entries here so far" if we
-access the root of the application (``/``). To do this, we add a new
-test method to our class, like this::
-
- class FlaskrTestCase(unittest.TestCase):
-
- def setUp(self):
- self.db_fd, flaskr.app.config['DATABASE'] = tempfile.mkstemp()
- self.app = flaskr.app.test_client()
- flaskr.init_db()
+access the root of the application (``/``). To do this, we add a new
+test function to :file:`test_flaskr.py`, like this::
- def tearDown(self):
- os.close(self.db_fd)
- os.unlink(flaskr.app.config['DATABASE'])
+ def test_empty_db(client):
+ """Start with a blank database."""
- def test_empty_db(self):
- rv = self.app.get('/')
- assert b'No entries here so far' in rv.data
+ rv = client.get('/')
+ assert b'No entries here so far' in rv.data
Notice that our test functions begin with the word `test`; this allows
-:mod:`unittest` to automatically identify the method as a test to run.
+`pytest`_ to automatically identify the function as a test to run.
-By using `self.app.get` we can send an HTTP ``GET`` request to the application with
+By using ``client.get`` we can send an HTTP ``GET`` request to the application with
the given path. The return value will be a :class:`~flask.Flask.response_class` object.
We can now use the :attr:`~werkzeug.wrappers.BaseResponse.data` attribute to inspect
the return value (as string) from the application. In this case, we ensure that
@@ -120,12 +128,15 @@ the return value (as string) from the application. In this case, we ensure that
Run it again and you should see one passing test::
- $ python flaskr_tests.py
- .
- ----------------------------------------------------------------------
- Ran 1 test in 0.034s
+ $ pytest -v
- OK
+ ================ test session starts ================
+ rootdir: ./flask/examples/flaskr, inifile: setup.cfg
+ collected 1 items
+
+ tests/test_flaskr.py::test_empty_db PASSED
+
+ ============= 1 passed in 0.10 seconds ==============
Logging In and Out
------------------
@@ -136,39 +147,47 @@ of the application. To do this, we fire some requests to the login and logout
pages with the required form data (username and password). And because the
login and logout pages redirect, we tell the client to `follow_redirects`.
-Add the following two methods to your `FlaskrTestCase` class::
+Add the following two functions to your :file:`test_flaskr.py` file::
+
+ def login(client, username, password):
+ return client.post('/login', data=dict(
+ username=username,
+ password=password
+ ), follow_redirects=True)
- def login(self, username, password):
- return self.app.post('/login', data=dict(
- username=username,
- password=password
- ), follow_redirects=True)
- def logout(self):
- return self.app.get('/logout', follow_redirects=True)
+ def logout(client):
+ return client.get('/logout', follow_redirects=True)
Now we can easily test that logging in and out works and that it fails with
-invalid credentials. Add this new test to the class::
-
- def test_login_logout(self):
- rv = self.login('admin', 'default')
- assert b'You were logged in' in rv.data
- rv = self.logout()
- assert b'You were logged out' in rv.data
- rv = self.login('adminx', 'default')
- assert b'Invalid username' in rv.data
- rv = self.login('admin', 'defaultx')
- assert b'Invalid password' in rv.data
+invalid credentials. Add this new test function::
+
+ def test_login_logout(client):
+ """Make sure login and logout works."""
+
+ rv = login(client, flaskr.app.config['USERNAME'], flaskr.app.config['PASSWORD'])
+ assert b'You were logged in' in rv.data
+
+ rv = logout(client)
+ assert b'You were logged out' in rv.data
+
+ rv = login(client, flaskr.app.config['USERNAME'] + 'x', flaskr.app.config['PASSWORD'])
+ assert b'Invalid username' in rv.data
+
+ rv = login(client, flaskr.app.config['USERNAME'], flaskr.app.config['PASSWORD'] + 'x')
+ assert b'Invalid password' in rv.data
Test Adding Messages
--------------------
-We should also test that adding messages works. Add a new test method
+We should also test that adding messages works. Add a new test function
like this::
- def test_messages(self):
- self.login('admin', 'default')
- rv = self.app.post('/add', data=dict(
+ def test_messages(client):
+ """Test that messages work."""
+
+ login(client, flaskr.app.config['USERNAME'], flaskr.app.config['PASSWORD'])
+ rv = client.post('/add', data=dict(
title='',
text='HTML allowed here'
), follow_redirects=True)
@@ -181,22 +200,25 @@ which is the intended behavior.
Running that should now give us three passing tests::
- $ python flaskr_tests.py
- ...
- ----------------------------------------------------------------------
- Ran 3 tests in 0.332s
+ $ pytest -v
- OK
+ ================ test session starts ================
+ rootdir: ./flask/examples/flaskr, inifile: setup.cfg
+ collected 3 items
+
+ tests/test_flaskr.py::test_empty_db PASSED
+ tests/test_flaskr.py::test_login_logout PASSED
+ tests/test_flaskr.py::test_messages PASSED
+
+ ============= 3 passed in 0.23 seconds ==============
For more complex tests with headers and status codes, check out the
`MiniTwit Example`_ from the sources which contains a larger test
suite.
-
.. _MiniTwit Example:
https://github.com/pallets/flask/tree/master/examples/minitwit/
-
Other Testing Tricks
--------------------
@@ -208,7 +230,7 @@ temporarily. With this you can access the :class:`~flask.request`,
functions. Here is a full example that demonstrates this approach::
import flask
-
+
app = flask.Flask(__name__)
with app.test_request_context('/?name=Peter'):
@@ -353,3 +375,81 @@ independently of the session backend used::
Note that in this case you have to use the ``sess`` object instead of the
:data:`flask.session` proxy. The object however itself will provide the
same interface.
+
+
+Testing JSON APIs
+-----------------
+
+.. versionadded:: 1.0
+
+Flask has great support for JSON, and is a popular choice for building JSON
+APIs. Making requests with JSON data and examining JSON data in responses is
+very convenient::
+
+ from flask import request, jsonify
+
+ @app.route('/api/auth')
+ def auth():
+ json_data = request.get_json()
+ email = json_data['email']
+ password = json_data['password']
+ return jsonify(token=generate_token(email, password))
+
+ with app.test_client() as c:
+ rv = c.post('/api/auth', json={
+ 'username': 'flask', 'password': 'secret'
+ })
+ json_data = rv.get_json()
+ assert verify_token(email, json_data['token'])
+
+Passing the ``json`` argument in the test client methods sets the request data
+to the JSON-serialized object and sets the content type to
+``application/json``. You can get the JSON data from the request or response
+with ``get_json``.
+
+
+.. _testing-cli:
+
+Testing CLI Commands
+--------------------
+
+Click comes with `utilities for testing`_ your CLI commands.
+
+Use :meth:`CliRunner.invoke ` to call
+commands in the same way they would be called from the command line. The
+:class:`~click.testing.CliRunner` runs the command in isolation and
+captures the output in a :class:`~click.testing.Result` object. ::
+
+ import click
+ from click.testing import CliRunner
+
+ @app.cli.command('hello')
+ @click.option('--name', default='World')
+ def hello_command(name)
+ click.echo(f'Hello, {name}!')
+
+ def test_hello():
+ runner = CliRunner()
+ result = runner.invoke(hello_command, ['--name', 'Flask'])
+ assert 'Hello, Flask' in result.output
+
+If you want to test how your command parses parameters, without running
+the command, use the command's :meth:`~click.BaseCommand.make_context`
+method. This is useful for testing complex validation rules and custom
+types. ::
+
+ def upper(ctx, param, value):
+ if value is not None:
+ return value.upper()
+
+ @app.cli.command('hello')
+ @click.option('--name', default='World', callback=upper)
+ def hello_command(name)
+ click.echo(f'Hello, {name}!')
+
+ def test_hello_params():
+ context = hello_command.make_context('hello', ['--name', 'flask'])
+ assert context.params['name'] == 'FLASK'
+
+.. _click: http://click.pocoo.org/
+.. _utilities for testing: http://click.pocoo.org/testing
diff --git a/docs/tutorial/dbcon.rst b/docs/tutorial/dbcon.rst
index 2dd3d7be..179c962b 100644
--- a/docs/tutorial/dbcon.rst
+++ b/docs/tutorial/dbcon.rst
@@ -3,6 +3,9 @@
Step 4: Database Connections
----------------------------
+Let's continue building our code in the ``flaskr.py`` file.
+(Scroll to the end of the page for more about project layout.)
+
You currently have a function for establishing a database connection with
`connect_db`, but by itself, it is not particularly useful. Creating and
closing database connections all the time is very inefficient, so you will
diff --git a/docs/tutorial/dbinit.rst b/docs/tutorial/dbinit.rst
index fbbcde00..484354ba 100644
--- a/docs/tutorial/dbinit.rst
+++ b/docs/tutorial/dbinit.rst
@@ -9,31 +9,37 @@ systems need a schema that tells them how to store that information.
Before starting the server for the first time, it's important to create
that schema.
-Such a schema can be created by piping the ``schema.sql`` file into the
-`sqlite3` command as follows::
+Such a schema could be created by piping the ``schema.sql`` file into the
+``sqlite3`` command as follows::
sqlite3 /tmp/flaskr.db < schema.sql
-The downside of this is that it requires the ``sqlite3`` command to be
-installed, which is not necessarily the case on every system. This also
-requires that you provide the path to the database, which can introduce
-errors. It's a good idea to add a function that initializes the database
-for you, to the application.
+However, the downside of this is that it requires the ``sqlite3`` command
+to be installed, which is not necessarily the case on every system. This
+also requires that you provide the path to the database, which can introduce
+errors.
-To do this, you can create a function and hook it into a :command:`flask`
-command that initializes the database. For now just take a look at the
-code segment below. A good place to add this function, and command, is
-just below the `connect_db` function in :file:`flaskr.py`::
+Instead of the ``sqlite3`` command above, it's a good idea to add a function
+to our application that initializes the database for you. To do this, you
+can create a function and hook it into a :command:`flask` command that
+initializes the database.
+
+Take a look at the code segment below. A good place to add this function,
+and command, is just below the ``connect_db`` function in :file:`flaskr.py`::
def init_db():
db = get_db()
+
with app.open_resource('schema.sql', mode='r') as f:
db.cursor().executescript(f.read())
+
db.commit()
+
@app.cli.command('initdb')
def initdb_command():
"""Initializes the database."""
+
init_db()
print('Initialized the database.')
@@ -59,7 +65,8 @@ On that cursor, there is a method to execute a complete script. Finally, you
only have to commit the changes. SQLite3 and other transactional
databases will not commit unless you explicitly tell it to.
-Now, it is possible to create a database with the :command:`flask` script::
+Now, in a terminal, from the application root directory :file:`flaskr/` it is
+possible to create a database with the :command:`flask` script::
flask initdb
Initialized the database.
diff --git a/docs/tutorial/folders.rst b/docs/tutorial/folders.rst
index ba62b3b7..23fefaec 100644
--- a/docs/tutorial/folders.rst
+++ b/docs/tutorial/folders.rst
@@ -3,8 +3,11 @@
Step 0: Creating The Folders
============================
-Before getting started, you will need to create the folders needed for this
-application::
+It is recommended to install your Flask application within a virtualenv. Please
+read the :ref:`installation` section to set up your environment.
+
+Now that you have installed Flask, you will need to create the folders required
+for this tutorial. Your directory structure will look like this::
/flaskr
/flaskr
@@ -13,9 +16,10 @@ application::
The application will be installed and run as Python package. This is the
recommended way to install and run Flask applications. You will see exactly
-how to run ``flaskr`` later on in this tutorial. For now go ahead and create
-the applications directory structure. In the next few steps you will be
-creating the database schema as well as the main module.
+how to run ``flaskr`` later on in this tutorial.
+
+For now go ahead and create the applications directory structure. In the next
+few steps you will be creating the database schema as well as the main module.
As a quick side note, the files inside of the :file:`static` folder are
available to users of the application via HTTP. This is the place where CSS and
diff --git a/docs/tutorial/index.rst b/docs/tutorial/index.rst
index f0a583e0..7eee5fa0 100644
--- a/docs/tutorial/index.rst
+++ b/docs/tutorial/index.rst
@@ -3,19 +3,19 @@
Tutorial
========
-You want to develop an application with Python and Flask? Here you have
-the chance to learn by example. In this tutorial, we will create a simple
-microblogging application. It only supports one user that can create
-text-only entries and there are no feeds or comments, but it still
-features everything you need to get started. We will use Flask and SQLite
-as a database (which comes out of the box with Python) so there is nothing
-else you need.
+Learn by example to develop an application with Python and Flask.
+
+In this tutorial, we will create a simple blogging application. It only
+supports one user, only allows text entries, and has no feeds or comments.
+
+While very simple, this example still features everything you need to get
+started. In addition to Flask, we will use SQLite for the database, which is
+built-in to Python, so there is nothing else you need.
If you want the full source code in advance or for comparison, check out
the `example source`_.
-.. _example source:
- https://github.com/pallets/flask/tree/master/examples/flaskr/
+.. _example source: https://github.com/pallets/flask/tree/master/examples/flaskr/
.. toctree::
:maxdepth: 2
diff --git a/docs/tutorial/introduction.rst b/docs/tutorial/introduction.rst
index dd46628b..ed984715 100644
--- a/docs/tutorial/introduction.rst
+++ b/docs/tutorial/introduction.rst
@@ -22,7 +22,12 @@ connections in a more intelligent way, allowing you to target different
relational databases at once and more. You might also want to consider
one of the popular NoSQL databases if your data is more suited for those.
-Here a screenshot of the final application:
+.. warning::
+ If you're following the tutorial from a specific version of the docs, be
+ sure to check out the same tag in the repository, otherwise the tutorial
+ may be different than the example.
+
+Here is a screenshot of the final application:
.. image:: ../_static/flaskr.png
:align: center
@@ -31,4 +36,4 @@ Here a screenshot of the final application:
Continue with :ref:`tutorial-folders`.
-.. _SQLAlchemy: http://www.sqlalchemy.org/
+.. _SQLAlchemy: https://www.sqlalchemy.org/
diff --git a/docs/tutorial/packaging.rst b/docs/tutorial/packaging.rst
index 8db6531e..e08f26fa 100644
--- a/docs/tutorial/packaging.rst
+++ b/docs/tutorial/packaging.rst
@@ -9,10 +9,10 @@ tutorial you will see exactly how to extend the ``flask`` command line
interface (CLI).
A useful pattern to manage a Flask application is to install your app
-following the `Python Packaging Guide`_. Presently this involves
-creating two new files; :file:`setup.py` and :file:`MANIFEST.in` in the
-projects root directory. You also need to add an :file:`__init__.py`
-file to make the :file:`flaskr/flaskr` directory a package. After these
+following the `Python Packaging Guide`_. Presently this involves
+creating two new files; :file:`setup.py` and :file:`MANIFEST.in` in the
+projects root directory. You also need to add an :file:`__init__.py`
+file to make the :file:`flaskr/flaskr` directory a package. After these
changes, your code structure should be::
/flaskr
@@ -25,9 +25,7 @@ changes, your code structure should be::
setup.py
MANIFEST.in
-The content of the ``setup.py`` file for ``flaskr`` is:
-
-.. sourcecode:: python
+Create the ``setup.py`` file for ``flaskr`` with the following content::
from setuptools import setup
@@ -43,53 +41,55 @@ The content of the ``setup.py`` file for ``flaskr`` is:
When using setuptools, it is also necessary to specify any special files
that should be included in your package (in the :file:`MANIFEST.in`).
In this case, the static and templates directories need to be included,
-as well as the schema. Create the :file:`MANIFEST.in` and add the
-following lines::
+as well as the schema.
+
+Create the :file:`MANIFEST.in` and add the following lines::
graft flaskr/templates
graft flaskr/static
include flaskr/schema.sql
-To simplify locating the application, add the following import statement
-into this file, :file:`flaskr/__init__.py`:
+Next, to simplify locating the application, create the file,
+:file:`flaskr/__init__.py` containing only the following import statement::
-.. sourcecode:: python
+ from .flaskr import app
- from flaskr import app
-
-This import statement brings the application instance into the top-level
-of the application package. When it is time to run the application, the
-Flask development server needs the location of the app instance. This
-import statement simplifies the location process. Without it the export
-statement a few steps below would need to be
+This import statement brings the application instance into the top-level
+of the application package. When it is time to run the application, the
+Flask development server needs the location of the app instance. This
+import statement simplifies the location process. Without the above
+import statement, the export statement a few steps below would need to be
``export FLASK_APP=flaskr.flaskr``.
At this point you should be able to install the application. As usual, it
is recommended to install your Flask application within a `virtualenv`_.
-With that said, go ahead and install the application with::
+With that said, from the ``flaskr/`` directory, go ahead and install the
+application with::
pip install --editable .
-The above installation command assumes that it is run within the projects
-root directory, `flaskr/`. The `editable` flag allows editing
-source code without having to reinstall the Flask app each time you make
-changes. The flaskr app is now installed in your virtualenv (see output
+The above installation command assumes that it is run within the projects
+root directory, ``flaskr/``. The ``editable`` flag allows editing
+source code without having to reinstall the Flask app each time you make
+changes. The flaskr app is now installed in your virtualenv (see output
of ``pip freeze``).
With that out of the way, you should be able to start up the application.
-Do this with the following commands::
+Do this on Mac or Linux with the following commands in ``flaskr/``::
export FLASK_APP=flaskr
- export FLASK_DEBUG=true
+ export FLASK_ENV=development
flask run
-(In case you are on Windows you need to use `set` instead of `export`).
-The :envvar:`FLASK_DEBUG` flag enables or disables the interactive debugger.
+(In case you are on Windows you need to use ``set`` instead of ``export``).
+Exporting ``FLASK_ENV=development`` turns on all development features
+such as enabling the interactive debugger.
+
*Never leave debug mode activated in a production system*, because it will
allow users to execute code on the server!
You will see a message telling you that server has started along with
-the address at which you can access it.
+the address at which you can access it in a browser.
When you head over to the server in your browser, you will get a 404 error
because we don't have any views yet. That will be addressed a little later,
diff --git a/docs/tutorial/setup.rst b/docs/tutorial/setup.rst
index 4bedb54c..5c69ecca 100644
--- a/docs/tutorial/setup.rst
+++ b/docs/tutorial/setup.rst
@@ -3,42 +3,46 @@
Step 2: Application Setup Code
==============================
-Now that the schema is in place, you can create the application module,
-:file:`flaskr.py`. This file should be placed inside of the
-:file:`flaskr/flaskr` folder. The first several lines of code in the
-application module are the needed import statements. After that there will be a
-few lines of configuration code. For small applications like ``flaskr``, it is
-possible to drop the configuration directly into the module. However, a cleaner
-solution is to create a separate ``.ini`` or ``.py`` file, load that, and
-import the values from there.
+Next, we will create the application module, :file:`flaskr.py`. Just like the
+:file:`schema.sql` file you created in the previous step, this file should be
+placed inside of the :file:`flaskr/flaskr` folder.
+
+For this tutorial, all the Python code we use will be put into this file
+(except for one line in ``__init__.py``, and any testing or optional files you
+decide to create).
+
+The first several lines of code in the application module are the needed import
+statements. After that there will be a few lines of configuration code.
+
+For small applications like ``flaskr``, it is possible to drop the configuration
+directly into the module. However, a cleaner solution is to create a separate
+``.py`` file, load that, and import the values from there.
Here are the import statements (in :file:`flaskr.py`)::
- # all the imports
import os
import sqlite3
- from flask import Flask, request, session, g, redirect, url_for, abort, \
- render_template, flash
-The next couple lines will create the actual application instance and
-initialize it with the config from the same file in :file:`flaskr.py`:
+ from flask import (Flask, request, session, g, redirect, url_for, abort,
+ render_template, flash)
-.. sourcecode:: python
+The next couple lines will create the actual application instance and
+initialize it with the config from the same file in :file:`flaskr.py`::
app = Flask(__name__) # create the application instance :)
app.config.from_object(__name__) # load config from this file , flaskr.py
# Load default config and override config from an environment variable
- app.config.update(dict(
+ app.config.update(
DATABASE=os.path.join(app.root_path, 'flaskr.db'),
- SECRET_KEY='development key',
+ SECRET_KEY=b'_5#y2L"F4Q8z\n\xec]/',
USERNAME='admin',
PASSWORD='default'
- ))
+ )
app.config.from_envvar('FLASKR_SETTINGS', silent=True)
-The :class:`~flask.Config` object works similarly to a dictionary, so it can be
-updated with new values.
+In the above code, the :class:`~flask.Config` object works similarly to a
+dictionary, so it can be updated with new values.
.. admonition:: Database Path
@@ -58,40 +62,40 @@ updated with new values.
Usually, it is a good idea to load a separate, environment-specific
configuration file. Flask allows you to import multiple configurations and it
will use the setting defined in the last import. This enables robust
-configuration setups. :meth:`~flask.Config.from_envvar` can help achieve this.
-
-.. sourcecode:: python
+configuration setups. :meth:`~flask.Config.from_envvar` can help achieve
+this. ::
app.config.from_envvar('FLASKR_SETTINGS', silent=True)
-Simply define the environment variable :envvar:`FLASKR_SETTINGS` that points to
-a config file to be loaded. The silent switch just tells Flask to not complain
-if no such environment key is set.
+If you want to do this (not required for this tutorial) simply define the
+environment variable :envvar:`FLASKR_SETTINGS` that points to a config file
+to be loaded. The silent switch just tells Flask to not complain if no such
+environment key is set.
In addition to that, you can use the :meth:`~flask.Config.from_object`
method on the config object and provide it with an import name of a
module. Flask will then initialize the variable from that module. Note
that in all cases, only variable names that are uppercase are considered.
-The ``SECRET_KEY`` is needed to keep the client-side sessions secure.
+The :data:`SECRET_KEY` is needed to keep the client-side sessions secure.
Choose that key wisely and as hard to guess and complex as possible.
-Lastly, you will add a method that allows for easy connections to the
-specified database. This can be used to open a connection on request and
-also from the interactive Python shell or a script. This will come in
-handy later. You can create a simple database connection through SQLite and
-then tell it to use the :class:`sqlite3.Row` object to represent rows.
-This allows the rows to be treated as if they were dictionaries instead of
-tuples.
-
-.. sourcecode:: python
+Lastly, add a method that allows for easy connections to the specified
+database. ::
def connect_db():
"""Connects to the specific database."""
+
rv = sqlite3.connect(app.config['DATABASE'])
rv.row_factory = sqlite3.Row
return rv
+This can be used to open a connection on request and also from the
+interactive Python shell or a script. This will come in handy later.
+You can create a simple database connection through SQLite and then tell
+it to use the :class:`sqlite3.Row` object to represent rows. This allows
+the rows to be treated as if they were dictionaries instead of tuples.
+
In the next section you will see how to run the application.
Continue with :ref:`tutorial-packaging`.
diff --git a/docs/tutorial/templates.rst b/docs/tutorial/templates.rst
index 269e8df1..12a555e7 100644
--- a/docs/tutorial/templates.rst
+++ b/docs/tutorial/templates.rst
@@ -15,7 +15,8 @@ escaped with their XML equivalents.
We are also using template inheritance which makes it possible to reuse
the layout of the website in all pages.
-Put the following templates into the :file:`templates` folder:
+Create the follwing three HTML files and place them in the
+:file:`templates` folder:
.. _Jinja2: http://jinja.pocoo.org/docs/templates
@@ -59,7 +60,7 @@ show_entries.html
This template extends the :file:`layout.html` template from above to display the
messages. Note that the ``for`` loop iterates over the messages we passed
in with the :func:`~flask.render_template` function. Notice that the form is
-configured to to submit to the `add_entry` view function and use ``POST`` as
+configured to submit to the `add_entry` view function and use ``POST`` as
HTTP method:
.. sourcecode:: html+jinja
@@ -79,9 +80,9 @@ HTTP method:
{% endif %}
{% for entry in entries %}
-
{{ entry.title }}
{{ entry.text|safe }}
+
{{ entry.title }}
{{ entry.text|safe }}
{% else %}
-
Unbelievable. No entries here so far
+
Unbelievable. No entries here so far
{% endfor %}
{% endblock %}
diff --git a/docs/tutorial/testing.rst b/docs/tutorial/testing.rst
index dcf36594..26099375 100644
--- a/docs/tutorial/testing.rst
+++ b/docs/tutorial/testing.rst
@@ -46,7 +46,7 @@ At this point you can run the tests. Here ``pytest`` will be used.
Run and watch the tests pass, within the top-level :file:`flaskr/`
directory as::
- py.test
+ pytest
Testing + setuptools
--------------------
diff --git a/docs/tutorial/views.rst b/docs/tutorial/views.rst
index 4364d973..1b09fcb8 100644
--- a/docs/tutorial/views.rst
+++ b/docs/tutorial/views.rst
@@ -4,7 +4,8 @@ Step 6: The View Functions
==========================
Now that the database connections are working, you can start writing the
-view functions. You will need four of them:
+view functions. You will need four of them; Show Entries, Add New Entry,
+Login and Logout. Add the following code snipets to :file:`flaskr.py`.
Show Entries
------------
diff --git a/docs/upgrading.rst b/docs/upgrading.rst
index 41b70f03..af2383c0 100644
--- a/docs/upgrading.rst
+++ b/docs/upgrading.rst
@@ -49,7 +49,7 @@ Any of the following is functionally equivalent::
response = send_file(open(fname), attachment_filename=fname)
response.set_etag(...)
-The reason for this is that some file-like objects have a invalid or even
+The reason for this is that some file-like objects have an invalid or even
misleading ``name`` attribute. Silently swallowing errors in such cases was not
a satisfying solution.
@@ -143,7 +143,7 @@ when there is no request context yet but an application context. The old
``flask.Flask.request_globals_class`` attribute was renamed to
:attr:`flask.Flask.app_ctx_globals_class`.
-.. _Flask-OldSessions: http://pythonhosted.org/Flask-OldSessions/
+.. _Flask-OldSessions: https://pythonhosted.org/Flask-OldSessions/
Version 0.9
-----------
@@ -198,7 +198,7 @@ applications with Flask. Because we want to make upgrading as easy as
possible we tried to counter the problems arising from these changes by
providing a script that can ease the transition.
-The script scans your whole application and generates an unified diff with
+The script scans your whole application and generates a unified diff with
changes it assumes are safe to apply. However as this is an automated
tool it won't be able to find all use cases and it might miss some. We
internally spread a lot of deprecation warnings all over the place to make
diff --git a/examples/flaskr/README b/examples/flaskr/README
index 90860ff2..ab668d67 100644
--- a/examples/flaskr/README
+++ b/examples/flaskr/README
@@ -9,17 +9,19 @@
~ How do I use it?
- 1. edit the configuration in the flaskr.py file or
- export an FLASKR_SETTINGS environment variable
- pointing to a configuration file.
+ 1. edit the configuration in the factory.py file or
+ export a FLASKR_SETTINGS environment variable
+ pointing to a configuration file or pass in a
+ dictionary with config values using the create_app
+ function.
2. install the app from the root of the project directory
pip install --editable .
- 3. Instruct flask to use the right application
+ 3. instruct flask to use the right application
- export FLASK_APP=flaskr
+ export FLASK_APP="flaskr.factory:create_app()"
4. initialize the database with this command:
diff --git a/examples/flaskr/flaskr/__init__.py b/examples/flaskr/flaskr/__init__.py
index 37a7b5cc..e69de29b 100644
--- a/examples/flaskr/flaskr/__init__.py
+++ b/examples/flaskr/flaskr/__init__.py
@@ -1 +0,0 @@
-from flaskr.flaskr import app
\ No newline at end of file
diff --git a/examples/flaskr/flaskr/blueprints/__init__.py b/examples/flaskr/flaskr/blueprints/__init__.py
new file mode 100644
index 00000000..e69de29b
diff --git a/examples/flaskr/flaskr/flaskr.py b/examples/flaskr/flaskr/blueprints/flaskr.py
similarity index 55%
rename from examples/flaskr/flaskr/flaskr.py
rename to examples/flaskr/flaskr/blueprints/flaskr.py
index b4c1d6bd..7b64dd9e 100644
--- a/examples/flaskr/flaskr/flaskr.py
+++ b/examples/flaskr/flaskr/blueprints/flaskr.py
@@ -10,29 +10,18 @@
:license: BSD, see LICENSE for more details.
"""
-import os
from sqlite3 import dbapi2 as sqlite3
-from flask import Flask, request, session, g, redirect, url_for, abort, \
- render_template, flash
+from flask import Blueprint, request, session, g, redirect, url_for, abort, \
+ render_template, flash, current_app
-# create our little application :)
-app = Flask(__name__)
-
-# Load default config and override config from an environment variable
-app.config.update(dict(
- DATABASE=os.path.join(app.root_path, 'flaskr.db'),
- DEBUG=True,
- SECRET_KEY='development key',
- USERNAME='admin',
- PASSWORD='default'
-))
-app.config.from_envvar('FLASKR_SETTINGS', silent=True)
+# create our blueprint :)
+bp = Blueprint('flaskr', __name__)
def connect_db():
"""Connects to the specific database."""
- rv = sqlite3.connect(app.config['DATABASE'])
+ rv = sqlite3.connect(current_app.config['DATABASE'])
rv.row_factory = sqlite3.Row
return rv
@@ -40,18 +29,11 @@ def connect_db():
def init_db():
"""Initializes the database."""
db = get_db()
- with app.open_resource('schema.sql', mode='r') as f:
+ with current_app.open_resource('schema.sql', mode='r') as f:
db.cursor().executescript(f.read())
db.commit()
-@app.cli.command('initdb')
-def initdb_command():
- """Creates the database tables."""
- init_db()
- print('Initialized the database.')
-
-
def get_db():
"""Opens a new database connection if there is none yet for the
current application context.
@@ -61,14 +43,7 @@ def get_db():
return g.sqlite_db
-@app.teardown_appcontext
-def close_db(error):
- """Closes the database again at the end of the request."""
- if hasattr(g, 'sqlite_db'):
- g.sqlite_db.close()
-
-
-@app.route('/')
+@bp.route('/')
def show_entries():
db = get_db()
cur = db.execute('select title, text from entries order by id desc')
@@ -76,7 +51,7 @@ def show_entries():
return render_template('show_entries.html', entries=entries)
-@app.route('/add', methods=['POST'])
+@bp.route('/add', methods=['POST'])
def add_entry():
if not session.get('logged_in'):
abort(401)
@@ -85,26 +60,26 @@ def add_entry():
[request.form['title'], request.form['text']])
db.commit()
flash('New entry was successfully posted')
- return redirect(url_for('show_entries'))
+ return redirect(url_for('flaskr.show_entries'))
-@app.route('/login', methods=['GET', 'POST'])
+@bp.route('/login', methods=['GET', 'POST'])
def login():
error = None
if request.method == 'POST':
- if request.form['username'] != app.config['USERNAME']:
+ if request.form['username'] != current_app.config['USERNAME']:
error = 'Invalid username'
- elif request.form['password'] != app.config['PASSWORD']:
+ elif request.form['password'] != current_app.config['PASSWORD']:
error = 'Invalid password'
else:
session['logged_in'] = True
flash('You were logged in')
- return redirect(url_for('show_entries'))
+ return redirect(url_for('flaskr.show_entries'))
return render_template('login.html', error=error)
-@app.route('/logout')
+@bp.route('/logout')
def logout():
session.pop('logged_in', None)
flash('You were logged out')
- return redirect(url_for('show_entries'))
+ return redirect(url_for('flaskr.show_entries'))
diff --git a/examples/flaskr/flaskr/factory.py b/examples/flaskr/flaskr/factory.py
new file mode 100644
index 00000000..7541ec3c
--- /dev/null
+++ b/examples/flaskr/flaskr/factory.py
@@ -0,0 +1,64 @@
+# -*- coding: utf-8 -*-
+"""
+ Flaskr
+ ~~~~~~
+
+ A microblog example application written as Flask tutorial with
+ Flask and sqlite3.
+
+ :copyright: (c) 2015 by Armin Ronacher.
+ :license: BSD, see LICENSE for more details.
+"""
+
+import os
+from flask import Flask, g
+from werkzeug.utils import find_modules, import_string
+from flaskr.blueprints.flaskr import init_db
+
+
+def create_app(config=None):
+ app = Flask('flaskr')
+
+ app.config.update(dict(
+ DATABASE=os.path.join(app.root_path, 'flaskr.db'),
+ DEBUG=True,
+ SECRET_KEY=b'_5#y2L"F4Q8z\n\xec]/',
+ USERNAME='admin',
+ PASSWORD='default'
+ ))
+ app.config.update(config or {})
+ app.config.from_envvar('FLASKR_SETTINGS', silent=True)
+
+ register_blueprints(app)
+ register_cli(app)
+ register_teardowns(app)
+
+ return app
+
+
+def register_blueprints(app):
+ """Register all blueprint modules
+
+ Reference: Armin Ronacher, "Flask for Fun and for Profit" PyBay 2016.
+ """
+ for name in find_modules('flaskr.blueprints'):
+ mod = import_string(name)
+ if hasattr(mod, 'bp'):
+ app.register_blueprint(mod.bp)
+ return None
+
+
+def register_cli(app):
+ @app.cli.command('initdb')
+ def initdb_command():
+ """Creates the database tables."""
+ init_db()
+ print('Initialized the database.')
+
+
+def register_teardowns(app):
+ @app.teardown_appcontext
+ def close_db(error):
+ """Closes the database again at the end of the request."""
+ if hasattr(g, 'sqlite_db'):
+ g.sqlite_db.close()
diff --git a/examples/flaskr/flaskr/templates/layout.html b/examples/flaskr/flaskr/templates/layout.html
index 737b51b2..862a9f4a 100644
--- a/examples/flaskr/flaskr/templates/layout.html
+++ b/examples/flaskr/flaskr/templates/layout.html
@@ -5,9 +5,9 @@