Flask

Software Screenshot:
Flask
Software Details:
Version: 0.10.1
Upload Date: 13 May 15
Developer: Armin Ronacher
Distribution Type: Freeware
Downloads: 125
Size: 531 Kb

Rating: 4.0/5 (Total Votes: 1)

Flask is intended for small scale applications being developed to be easy on CPU usage.

Features:

  • Built in development server and debugger
  • Integrated support for unittesting support
  • RESTful request dispatching
  • Uses Jinja2 templating
  • Support for secure cookies (client side sessions)
  • 100% WSGI 1.0 compliant
  • Unicode based
  • Extensively documented

What is new in this release:

  • Added support for byte strings back to the session system. This broke compatibility with the common case of people putting binary data for token verification into the session.
  • Fixed an issue where registering the same method twice for the same endpoint would trigger an exception incorrectly.

What is new in version 0.9:

  • Fixed an assumption in sessions implementation which could break message flashing on sessions implementations which use external storage.
  • Changed the behavior of tuple return values from functions. They are no longer arguments to the response object, they now have a defined meaning.
  • Added :attr:`flask.Flask.request_globals_class` to allow a specific class to be used on creation of the :data:`~flask.g` instance of each request.
  • Added `required_methods` attribute to view functions to force-add methods on registration.
  • Added :func:`flask.after_this_request`.
  • Added :func:`flask.stream_with_context` and the ability to push contexts multiple times without producing unexpected behavior.

What is new in version 0.8:

  • 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 as defaults.
  • Added :attr:`flask.views.View.decorators` to support simpler decorating of pluggable (class based) views.
  • Fixed an issue where the test client if used with the with statement did not trigger the execution of the teardown handlers.
  • Added finer control over the session cookie parameters.
  • HEAD requests to a method view now automatically dispatch to the `get` method if no handler was implemented.
  • Implemented the virtual :mod:`flask.ext` package to import extension from.
  • The context preservation on exceptions is now an integral component of Flask itself and no longer of the test client. This cleaned up some internal logic and lowers the odds of runaway request contexts in unittests.

What is new in version 0.7.2:

  • Fixed an issue with URL processors not properly working on blueprints.

What is new in version 0.7.1:

  • Bugfix release:
  • Added missing future import that broke 2.5 compatibility.
  • Fixed an infinite redirect issue with blueprints.

What is new in version 0.6.1:

  • Fixed an issue where the default `OPTIONS` response was not exposing all valid methods in the `Allow` header.
  • Jinja2 template loading syntax now allows "./" in front of a template load path. Previously this caused issues with module setups.
  • Fixed an issue where the subdomain setting for modules was ignored for the static folder.
  • Fixed a security problem that allowed clients to download arbitrary files if the host server was a windows based operating system and the client uses backslashes to escape the directory the files where exposed from.

What is new in version 0.6:

  • After request functions are now called in reverse order of registration.
  • OPTIONS is now automatically implemented by Flask unless the application explictly adds 'OPTIONS' as method to the URL rule. In this case no automatic OPTIONS handling kicks in.
  • Static rules are now even in place if there is no static folder for the module. This was implemented to aid GAE which will remove the static folder if it's part of a mapping in the .yml file.
  • The :attr:`~flask.Flask.config` is now available in the templates as `config`.
  • Context processors will no longer override values passed directly to the render function.
  • Added the ability to limit the incoming request data with the new ``MAX_CONTENT_LENGTH`` configuration value.
  • The endpoint for the :meth:`flask.Module.add_url_rule` method is now optional to be consistent with the function of the same name on the application object.
  • Added a :func:`flask.make_response` function that simplifies creating response object instances in views.
  • Added signalling support based on blinker. This feature is currently optional and supposed to be used by extensions and applications. If you want to use it, make sure to have `blinker`_ installed.
  • Refactored the way url adapters are created. This process is now fully customizable with the :meth:`~flask.Flask.create_url_adapter` method.
  • Modules can now register for a subdomain instead of just an URL prefix. This makes it possible to bind a whole module to a configurable subdomain.

What is new in version 0.5.1:

  • Fixes an issue with template loading from directories when modules where used.

What is new in version 0.4:

  • Added the ability to register application wide error handlers from modules.
  • :meth:`~flask.Flask.after_request` handlers are now also invoked if the request dies with an exception and an error handling page kicks in.
  • Test client has not the ability to preserve the request context for a little longer. This can also be used to trigger custom requests that do not pop the request stack for testing.
  • Because the Python standard library caches loggers, the name of the logger is configurable now to better support unittests.
  • Added `TESTING` switch that can activate unittesting helpers.
  • The logger switches to `DEBUG` mode now if debug is enabled.

Requirements:

  • Jinja 2.4 or higher
  • Werkzeug 0.6.1 or higher

Similar Software

TYPO3 Flow
TYPO3 Flow

1 Oct 15

XPSPL
XPSPL

13 Apr 15

Spring Web Flow
Spring Web Flow

9 Apr 16

Joomla! Framework
Joomla! Framework

13 May 15

Other Software of Developer Armin Ronacher

Werkzeug
Werkzeug

12 Apr 15

Logbook
Logbook

12 May 15

Pygments
Pygments

1 Mar 15

Comments to Flask

Comments not found
Add Comment
Turn on images!