More docstrings for blueprints.

This commit is contained in:
Armin Ronacher 2011-06-17 20:27:25 +02:00
parent dbb9a2ed46
commit 86175054d6
4 changed files with 40 additions and 11 deletions

View file

@ -18,10 +18,10 @@ Application Object
:inherited-members:
Module Objects
--------------
Blueprint Objects
-----------------
.. autoclass:: Module
.. autoclass:: Blueprint
:members:
:inherited-members:
@ -350,6 +350,9 @@ Useful Internals
if ctx is not None:
return ctx.session
.. autoclass:: flask.blueprints.BlueprintSetupState
:members:
Signals
-------

View file

@ -3,8 +3,8 @@
Application Factories
=====================
If you are already using packages and modules for your application
(:ref:`packages`) there are a couple of really nice ways to further improve
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 module is imported. But if you move the creation of this object,
into a function, you can then create multiple instances of this and later.

View file

@ -381,8 +381,7 @@ package it's actually inside your package:
/hello.html
For templates you can use the full power of Jinja2 templates. Head over
to the :ref:`templating` section of the documentation or the official
`Jinja2 Template Documentation
to the the official `Jinja2 Template Documentation
<http://jinja.pocoo.org/2/documentation/templates>`_ for more information.
Here is an example template: