Do not suggest deprecated flask.ext.*
This commit is contained in:
parent
09973a7387
commit
88111ae6bf
1 changed files with 0 additions and 8 deletions
|
|
@ -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
|
This is how users can then register dependencies to your extension in
|
||||||
their :file:`setup.py` files.
|
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
|
But what do extensions look like themselves? An extension has to ensure
|
||||||
that it works with multiple Flask application instances at once. This is
|
that it works with multiple Flask application instances at once. This is
|
||||||
a requirement because many people will use patterns like the
|
a requirement because many people will use patterns like the
|
||||||
|
|
@ -393,8 +387,6 @@ extension to be approved you have to follow these guidelines:
|
||||||
Python 2.7
|
Python 2.7
|
||||||
|
|
||||||
|
|
||||||
.. _ext-import-transition:
|
|
||||||
|
|
||||||
Extension Import Transition
|
Extension Import Transition
|
||||||
---------------------------
|
---------------------------
|
||||||
|
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue