maya-chen/flask
1
0
Fork 0
forked from orbit-oss/flask
Code Pull requests Activity

1.0 -> 0.11 in the docs

Browse source
This commit is contained in:
Armin Ronacher 2016-05-26 20:52:17 +02:00
parent 1df426aaaa
commit f9ea3fe026
7 changed files with 21 additions and 11 deletions
Download patch file Download diff file Expand all files Collapse all files

2
docs/api.rst
View file

@ -289,7 +289,7 @@ thing, like it does for :class:`request` and :class:`session`.
It's now also possible to use the ``in`` operator on it to see if an It's now also possible to use the ``in`` operator on it to see if an
attribute is defined and it yields all keys on iteration. attribute is defined and it yields all keys on iteration.
As of 1.0 you can use :meth:`pop` and :meth:`setdefault` in the same As of 0.11 you can use :meth:`pop` and :meth:`setdefault` in the same
way you would use them on a dictionary. way you would use them on a dictionary.
This is a proxy. See :ref:`notes-on-proxies` for more information. This is a proxy. See :ref:`notes-on-proxies` for more information.

2
docs/cli.rst
View file

@ -7,7 +7,7 @@ Command Line Interface
.. currentmodule:: flask .. currentmodule:: flask
One of the nice new features in Flask 1.0 is the built-in integration of One of the nice new features in Flask 0.11 is the built-in integration of
the `click <http://click.pocoo.org/>`_ command line interface. This the `click <http://click.pocoo.org/>`_ command line interface. This
enables a wide range of new features for the Flask ecosystem and your own enables a wide range of new features for the Flask ecosystem and your own
applications. applications.

2
docs/errorhandling.rst
View file

@ -131,7 +131,7 @@ Logging to a File
Even if you get mails, you probably also want to log warnings. It's a 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 good idea to keep as much information around that might be required to
debug a problem. By default as of Flask 1.0, errors are logged to your 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 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 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. your responsibility to warn in the code if something seems odd.

4
docs/extensiondev.rst
View file

@ -408,8 +408,8 @@ Flask 0.8 introduced a redirect import system as a compatibility aid for app
developers: Importing ``flask.ext.foo`` would try ``flask_foo`` and developers: Importing ``flask.ext.foo`` would try ``flask_foo`` and
``flaskext.foo`` in that order. ``flaskext.foo`` in that order.
As of Flask 1.0, most Flask extensions have transitioned to the new naming As of Flask 0.11, most Flask extensions have transitioned to the new naming
schema. The ``flask.ext.foo`` compatibility alias is still in Flask 1.0 but is schema. The ``flask.ext.foo`` compatibility alias is still in Flask 0.11 but is
now deprecated -- you should use ``flask_foo``. now deprecated -- you should use ``flask_foo``.

2
docs/server.rst
View file

@ -5,7 +5,7 @@ Development Server
.. currentmodule:: flask .. currentmodule:: flask
Starting with Flask 1.0 there are multiple built-in ways to run a Starting with Flask 0.11 there are multiple built-in ways to run a
development server. The best one is the :command:`flask` command line utility development server. The best one is the :command:`flask` command line utility
but you can also continue using the :meth:`Flask.run` method. but you can also continue using the :meth:`Flask.run` method.

2
docs/shell.rst
View file

@ -29,7 +29,7 @@ chapter of the documentation first.
Command Line Interface Command Line Interface
---------------------- ----------------------
Starting with Flask 1.0 the recommended way to work with the shell is the Starting with Flask 0.11 the recommended way to work with the shell is the
``flask shell`` command which does a lot of this automatically for you. ``flask shell`` command which does a lot of this automatically for you.
For instance the shell is automatically initialized with a loaded For instance the shell is automatically initialized with a loaded
application context. application context.

18
docs/upgrading.rst
View file

@ -21,13 +21,23 @@ installation, make sure to pass it the :option:`-U` parameter::
.. _upgrading-to-10: .. _upgrading-to-10:
Version 1.0 Version 0.11
----------- ------------
0.11 is an odd release in the Flask release cycle because it was supposed
to be the 1.0 release. However because there was such a long lead time up
to the release we decided to push out a 0.11 release first with some
changes removed to make the transition easier. If you have been tracking
the master branch which was 1.0 you might see some unexpected changes.
In case you did track the master branch you will notice that `flask --app`
is removed now. You need to use the environment variable to specify an
application.
Debugging Debugging
````````` `````````
Flask 1.0 removed the ``debug_log_format`` attribute from Flask Flask 0.11 removed the ``debug_log_format`` attribute from Flask
applications. Instead the new ``LOGGER_HANDLER_POLICY`` configuration can applications. Instead the new ``LOGGER_HANDLER_POLICY`` configuration can
be used to disable the default log handlers and custom log handlers can be be used to disable the default log handlers and custom log handlers can be
set up. set up.
@ -206,7 +216,7 @@ before, you should catch them with :exc:`RuntimeError` now.
Additionally the :func:`~flask.send_file` function is now issuing Additionally the :func:`~flask.send_file` function is now issuing
deprecation warnings if you depend on functionality that will be removed deprecation warnings if you depend on functionality that will be removed
in Flask 1.0. Previously it was possible to use etags and mimetypes in Flask 0.11. Previously it was possible to use etags and mimetypes
when file objects were passed. This was unreliable and caused issues when file objects were passed. This was unreliable and caused issues
for a few setups. If you get a deprecation warning, make sure to for a few setups. If you get a deprecation warning, make sure to
update your application to work with either filenames there or disable update your application to work with either filenames there or disable