A microframework based on Werkzeug, Jinja2 and good intentions
Flask is a microframework for Python based on Werkzeug, Jinja 2 and good
intentions. And before you ask: It's BSD licensed!
- Developed at devel:languages:python:flask
- Sources inherited from project openSUSE:Factory
-
13
derived packages
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout openSUSE:Leap:16.0:FactoryCandidates/python-Flask && cd $_
- Create Badge
Refresh
Refresh
Source Files
Filename | Size | Changed |
---|---|---|
Flask-0.8.tar.gz | 0000494211 483 KB | |
python-Flask.changes | 0000003173 3.1 KB | |
python-Flask.spec | 0000002329 2.27 KB |
Revision 5 (latest revision is 41)
Stephan Kulow (coolo)
accepted
request 90912
from
Sascha Peilicke (saschpe)
(revision 5)
- Update to version 0.8: * Refactored session support into a session interface so that the implementation of the sessions can be changed without having to override the Flask class. * Empty session cookies are now deleted properly automatically. * View functions can now opt out of getting the automatic OPTIONS implementation. * HTTP exceptions and Bad Request errors can now be trapped so that they show up normally in the traceback. * Flask in debug mode is now detecting some common problems and tries to warn you about them. * Flask in debug mode will now complain with an assertion error if a view was attached after the first request was handled. This gives earlier feedback when users forget to import view code ahead of time. * Added the ability to register callbacks that are only triggered once at the beginning of the first request. (:meth:`Flask.before_first_request`) * Malformed JSON data will now trigger a bad request HTTP exception instead of a value error which usually would result in a 500 internal server error if not handled. This is a backwards incompatible change. * Applications now not only have a root path where the resources and modules are located but also an instane path which is the designated place to drop files that are modified at runtime (uploads etc.). Also this is conceptionally only instance depending and outside version control so it's the perfect place to put configuration files etc. For more information see :ref:`instance-folders`. * Added the ``APPLICATION_ROOT`` configuration variable. * Implemented :meth:`~flask.testing.TestClient.session_transaction` to easily modify sessions from the test environment. * Refactored test client internally. The ``APPLICATION_ROOT`` configuration variable as well as ``SERVER_NAME`` are now properly used by the test client
Comments 0