Flask Changelog¶

Version 1.0.2¶

Released on May 2nd 2018

• Fix more backwards compatibility issues with merging slashes betweena blueprint prefix and route. (#2748)
• Fix error with flask routes command when there are no routes.(#2751)

Version 1.0.1¶

Released on April 29th 2018

• Fix registering partials (with no name) as view functions.(#2730)
• Don’t treat lists returned from view functions the same as tuples.Only tuples are interpreted as response data. (#2736)
• Extra slashes between a blueprint’s url_prefix and a route URLare merged. This fixes some backwards compatibility issues with thechange in 1.0. (#2731, #2742)
• Only trap BadRequestKeyError errors in debug mode, not allBadRequest errors. This allows abort(400) to continueworking as expected. (#2735)
• The FLASK_SKIP_DOTENV environment variable can be set to 1to skip automatically loading dotenv files. (#2722)

Version 1.0¶

Released on April 26th 2018

• Python 2.6 and 3.3 are no longer supported. (pallets/meta#24)
• Bump minimum dependency versions to the latest stable versions:Werkzeug >= 0.14, Jinja >= 2.10, itsdangerous >= 0.24, Click >= 5.1.(#2586)
• Skip app.run when a Flask application is runfrom the command line. This avoids some behavior that was confusingto debug.
• Change the default for JSONIFY_PRETTYPRINT_REGULAR toFalse. jsonify() returns a compact format bydefault, and an indented format in debug mode. (#2193)
• Flask.init accepts the host_matchingargument and sets it on url_map. (#1559)
• Flask.init accepts the static_host argumentand passes it as the host argument when defining the staticroute. (#1559)
• send_file() supports Unicode in attachment_filename.(#2223)
• Pass _scheme argument from url_for() tohandle_url_build_error(). (#2017)
• add_url_rule() accepts theprovide_automatic_options argument to disable adding theOPTIONS method. (#1489)
• MethodView subclasses inherit method handlers frombase classes. (#1936)
• Errors caused while opening the session at the beginning of therequest are handled by the app’s error handlers. (#2254)
• Blueprints gained json_encoder andjson_decoder attributes to override the app’sencoder and decoder. (#1898)
• Flask.make_response() raises TypeError instead ofValueError for bad response types. The error messages have beenimproved to describe why the type is invalid. (#2256)
• Add routes CLI command to output routes registered on theapplication. (#2259)
• Show warning when session cookie domain is a bare hostname or an IPaddress, as these may not behave properly in some browsers, such asChrome. (#2282)
• Allow IP address as exact session cookie domain. (#2282)
• SESSION_COOKIE_DOMAIN is set if it is detected throughSERVER_NAME. (#2282)
• Auto-detect zero-argument app factory called create_app ormake_app from FLASK_APP. (#2297)
• Factory functions are not required to take a script_infoparameter to work with the flask command. If they take a singleparameter or a parameter named script_info, theScriptInfo object will be passed. (#2319)
• FLASK_APP can be set to an app factory, with arguments ifneeded, for example FLASK_APP=myproject.app:create_app('dev').(#2326)
• FLASK_APP can point to local packages that are not installed ineditable mode, although pip install -e is still preferred.(#2414)
• The View class attributeprovide_automatic_options is set inas_view(), to be detected byadd_url_rule(). (#2316)
• Error handling will try handlers registered for blueprint, code,app, code, blueprint, exception, app, exception.(#2314)
• Cookie is added to the response’s Vary header if the sessionis accessed at all during the request (and not deleted). (#2288)
• test_request_context() accepts subdomain andurl_scheme arguments for use when building the base URL.(#1621)
• Set APPLICATION_ROOT to '/' by default. This was alreadythe implicit default when it was set to None.
• TRAP_BAD_REQUEST_ERRORS is enabled by default in debug mode.BadRequestKeyError has a message with the bad key in debug modeinstead of the generic bad request message. (#2348)
• Allow registering new tags withTaggedJSONSerializer to support storing othertypes in the session cookie. (#2352)
• Only open the session if the request has not been pushed onto thecontext stack yet. This allows stream_with_context()generators to access the same session that the containing view uses.(#2354)
• Add json keyword argument for the test client request methods.This will dump the given object as JSON and set the appropriatecontent type. (#2358)
• Extract JSON handling to a mixin applied to both theRequest and Response classes. This adds theis_json() and get_json() methods tothe response to make testing JSON response much easier. (#2358)
• Removed error handler caching because it caused unexpected resultsfor some exception inheritance hierarchies. Register handlersexplicitly for each exception if you want to avoid traversing theMRO. (#2362)
• Fix incorrect JSON encoding of aware, non-UTC datetimes. (#2374)
• Template auto reloading will honor debug mode even even ifjinja_env was already accessed. (#2373)
• The following old deprecated code was removed. (#2385)
  • flask.ext - import extensions directly by their name insteadof through the flask.ext namespace. For example,import flask.ext.sqlalchemy becomesimport flask_sqlalchemy.
  • Flask.init_jinja_globals - extendFlask.create_jinja_environment() instead.
  • Flask.error_handlers - tracked byFlask.error_handler_spec, use Flask.errorhandler()to register handlers.
  • Flask.request_globals_class - useFlask.app_ctx_globals_class instead.
  • Flask.static_path - use Flask.static_url_pathinstead.
  • Request.module - use Request.blueprint instead.
• The Request.json property is no longer deprecated.(#1421)
• Support passing a EnvironBuilder ordict to test_client.open.(#2412)
• The flask command and Flask.run() will load environmentvariables from .env and .flaskenv files if python-dotenv isinstalled. (#2416)
• When passing a full URL to the test client, the scheme in the URL isused instead of PREFERRED_URL_SCHEME. (#2430)
• Flask.logger has been simplified. LOGGER_NAME andLOGGER_HANDLER_POLICY config was removed. The logger is alwaysnamed flask.app. The level is only set on first access, itdoesn’t check Flask.debug each time. Only one format isused, not different ones depending on Flask.debug. Nohandlers are removed, and a handler is only added if no handlers arealready configured. (#2436)
• Blueprint view function names may not contain dots. (#2450)
• Fix a ValueError caused by invalid Range requests in somecases. (#2526)
• The development server uses threads by default. (#2529)
• Loading config files with silent=True will ignoreENOTDIR errors. (#2581)
• Pass —cert and —key options to flask run to run thedevelopment server over HTTPS. (#2606)
• Added SESSION_COOKIE_SAMESITE to control the SameSiteattribute on the session cookie. (#2607)
• Added test_cli_runner() to create a Click runnerthat can invoke Flask CLI commands for testing. (#2636)
• Subdomain matching is disabled by default and settingSERVER_NAME does not implicily enable it. It can be enabledby passing subdomain_matching=True to the Flask constructor.(#2635)
• A single trailing slash is stripped from the blueprinturl_prefix when it is registered with the app. (#2629)
• Request.get_json() doesn’t cache theresult if parsing fails when silent is true. (#2651)
• Request.get_json() no longer accepts arbitrary encodings.Incoming JSON should be encoded using UTF-8 per RFC 8259, butFlask will autodetect UTF-8, -16, or -32. (#2691)
• Added MAX_COOKIE_SIZE and Response.max_cookie_sizeto control when Werkzeug warns about large cookies that browsers mayignore. (#2693)
• Updated documentation theme to make docs look better in smallwindows. (#2709)
• Rewrote the tutorial docs and example project to take a morestructured approach to help new users avoid common pitfalls.(#2676)

Version 0.12.3¶

Released on April 26th 2018

• Request.get_json() no longer accepts arbitrary encodings.Incoming JSON should be encoded using UTF-8 per RFC 8259, butFlask will autodetect UTF-8, -16, or -32. (#2692)
• Fix a Python warning about imports when using python -m flask.(#2666)
• Fix a ValueError caused by invalid Range requests in somecases.

Version 0.12.2¶

Released on May 16 2017

• Fix a bug in safe_join on Windows.

Version 0.12.1¶

Bugfix release, released on March 31st 2017

• Prevent flask run from showing a NoAppException when an ImportError occurswithin the imported application module.
• Fix encoding behavior of app.config.from_pyfile for Python 3. Fix#2118.
• Use the SERVER_NAME config if it is present as default values forapp.run. #2109, #2152
• Call ctx.auto_pop with the exception object instead of None, in theevent that a BaseException such as KeyboardInterrupt is raised in arequest handler.

Version 0.12¶

Released on December 21st 2016, codename Punsch.

• the cli command now responds to –version.
• Mimetype guessing and ETag generation for file-like objects in send_filehas been removed, as per issue #104. See pull request #1849.
• Mimetype guessing in send_file now fails loudly and doesn’t fall back toapplication/octet-stream. See pull request #1988.
• Make flask.safe_join able to join multiple paths like os.path.join(pull request #1730).
• Revert a behavior change that made the dev server crash instead of returninga Internal Server Error (pull request #2006).
• Correctly invoke response handlers for both regular request dispatching aswell as error handlers.
• Disable logger propagation by default for the app logger.
• Add support for range requests in send_file.
• app.test_client includes preset default environment, which can now bedirectly set, instead of per client.get.

Version 0.11.2¶

Bugfix release, unreleased

• Fix crash when running under PyPy3, see pull request #1814.

Version 0.11.1¶

Bugfix release, released on June 7th 2016.

• Fixed a bug that prevented FLASKAPP=foobar/_init.py from working. Seepull request #1872.

Version 0.11¶

Released on May 29th 2016, codename Absinthe.

• Added support to serializing top-level arrays to flask.jsonify(). Thisintroduces a security risk in ancient browsers. SeeJSON 安全 for details.
• Added before_render_template signal.
• Added **kwargs to flask.Test.test_client() to support passingadditional keyword arguments to the constructor offlask.Flask.test_client_class.
• Added SESSION_REFRESH_EACH_REQUEST config key that controls theset-cookie behavior. If set to True a permanent session will berefreshed each request and get their lifetime extended, if set toFalse it will only be modified if the session actually modifies.Non permanent sessions are not affected by this and will alwaysexpire if the browser window closes.
• Made Flask support custom JSON mimetypes for incoming data.
• Added support for returning tuples in the form (response, headers)from a view function.
• Added flask.Config.from_json().
• Added flask.Flask.config_class.
• Added flask.Config.get_namespace().
• Templates are no longer automatically reloaded outside of debug mode. Thiscan be configured with the new TEMPLATES_AUTO_RELOAD config key.
• Added a workaround for a limitation in Python 3.3’s namespace loader.
• Added support for explicit root paths when using Python 3.3’s namespacepackages.
• Added flask and the flask.cli module to start the localdebug server through the click CLI system. This is recommended over the oldflask.run() method as it works faster and more reliable due to adifferent design and also replaces Flask-Script.
• Error handlers that match specific classes are now checked first,thereby allowing catching exceptions that are subclasses of HTTPexceptions (in werkzeug.exceptions). This makes it possiblefor an extension author to create exceptions that will by defaultresult in the HTTP error of their choosing, but may be caught witha custom error handler if desired.
• Added flask.Config.from_mapping().
• Flask will now log by default even if debug is disabled. The log format isnow hardcoded but the default log handling can be disabled through theLOGGER_HANDLER_POLICY configuration key.
• Removed deprecated module functionality.
• Added the EXPLAIN_TEMPLATE_LOADING config flag which when enabled willinstruct Flask to explain how it locates templates. This should helpusers debug when the wrong templates are loaded.
• Enforce blueprint handling in the order they were registered for templateloading.
• Ported test suite to py.test.
• Deprecated request.json in favour of request.get_json().
• Add “pretty” and “compressed” separators definitions in jsonify() method.Reduces JSON response size when JSONIFY_PRETTYPRINT_REGULAR=False by removingunnecessary white space included by default after separators.
• JSON responses are now terminated with a newline character, because it is aconvention that UNIX text files end with a newline and some clients don’tdeal well when this newline is missing. Seehttps://github.com/pallets/flask/pull/1262 – this came up originally as apart of https://github.com/kennethreitz/httpbin/issues/168
• The automatically provided OPTIONS method is now correctly disabled ifthe user registered an overriding rule with the lowercase-versionoptions (issue #1288).
• flask.json.jsonify now supports the datetime.date type (pull request#1326).
• Don’t leak exception info of already catched exceptions to context teardownhandlers (pull request #1393).
• Allow custom Jinja environment subclasses (pull request #1422).
• Updated extension dev guidelines.
• flask.g now has pop() and setdefault methods.
• Turn on autoescape for flask.templating.render_template_string by default(pull request #1515).
• flask.ext is now deprecated (pull request #1484).
• send_from_directory now raises BadRequest if the filename is invalid onthe server OS (pull request #1763).
• Added the JSONIFY_MIMETYPE configuration variable (pull request #1728).
• Exceptions during teardown handling will no longer leave bad applicationcontexts lingering around.

Version 0.10.2¶

(bugfix release, release date to be announced)

• Fixed broken test_appcontext_signals() test case.
• Raise an AttributeError in flask.helpers.findpackage() with auseful message explaining why it is raised when a PEP 302 import hook is usedwithout an _is_package() method.
• Fixed an issue causing exceptions raised before entering a request or appcontext to be passed to teardown handlers.
• Fixed an issue with query parameters getting removed from requests inthe test client when absolute URLs were requested.
• Made @before_first_request into a decorator as intended.
• Fixed an etags bug when sending a file streams with a name.
• Fixed send_from_directory not expanding to the application root pathcorrectly.
• Changed logic of before first request handlers to flip the flag afterinvoking. This will allow some uses that are potentially dangerous butshould probably be permitted.
• Fixed Python 3 bug when a handler from app.url_build_error_handlers_reraises the _BuildError.

Version 0.10.1¶

(bugfix release, released on June 14th 2013)

• Fixed an issue where |tojson was not quoting single quotes whichmade the filter not work properly in HTML attributes. Now it’spossible to use that filter in single quoted attributes. This shouldmake using that filter with angular.js easier.
• Added support for byte strings back to the session system. This brokecompatibility with the common case of people putting binary data fortoken verification into the session.
• Fixed an issue where registering the same method twice for the same endpointwould trigger an exception incorrectly.

Version 0.10¶

Released on June 13th 2013, codename Limoncello.

• Changed default cookie serialization format from pickle to JSON tolimit the impact an attacker can do if the secret key leaks. SeeVersion 0.10 for more information.
• Added template_test methods in addition to the already existingtemplate_filter method family.
• Added template_global methods in addition to the already existingtemplate_filter method family.
• Set the content-length header for x-sendfile.
• tojson filter now does not escape script blocks in HTML5 parsers.
• tojson used in templates is now safe by default due. This wasallowed due to the different escaping behavior.
• Flask will now raise an error if you attempt to register a new functionon an already used endpoint.
• Added wrapper module around simplejson and added default serializationof datetime objects. This allows much easier customization of howJSON is handled by Flask or any Flask extension.
• Removed deprecated internal flask.session module alias. Useflask.sessions instead to get the session module. This is not tobe confused with flask.session the session proxy.
• Templates can now be rendered without request context. The behavior isslightly different as the request, session and g objectswill not be available and blueprint’s context processors are notcalled.
• The config object is now available to the template as a real global andnot through a context processor which makes it available even in importedtemplates by default.
• Added an option to generate non-ascii encoded JSON which should resultin less bytes being transmitted over the network. It’s disabled bydefault to not cause confusion with existing libraries that might expectflask.json.dumps to return bytestrings by default.
• flask.g is now stored on the app context instead of the requestcontext.
• flask.g now gained a get() method for not erroring out on nonexisting items.
• flask.g now can be used with the in operator to see what’s definedand it now is iterable and will yield all attributes stored.
• flask.Flask.request_globals_class got renamed toflask.Flask.app_ctx_globals_class which is a better name to what itdoes since 0.10.
• request, session and g are now also added as proxies to the templatecontext which makes them available in imported templates. One has to bevery careful with those though because usage outside of macros mightcause caching.
• Flask will no longer invoke the wrong error handlers if a proxyexception is passed through.
• Added a workaround for chrome’s cookies in localhost not workingas intended with domain names.
• Changed logic for picking defaults for cookie values from sessionsto work better with Google Chrome.
• Added message_flashed signal that simplifies flashing testing.
• Added support for copying of request contexts for better working withgreenlets.
• Removed custom JSON HTTP exception subclasses. If you were relying on themyou can reintroduce them again yourself trivially. Using them however isstrongly discouraged as the interface was flawed.
• Python requirements changed: requiring Python 2.6 or 2.7 now to preparefor Python 3.3 port.
• Changed how the teardown system is informed about exceptions. This is nowmore reliable in case something handles an exception halfway throughthe error handling process.
• Request context preservation in debug mode now keeps the exceptioninformation around which means that teardown handlers are able todistinguish error from success cases.
• Added the JSONIFY_PRETTYPRINT_REGULAR configuration variable.
• Flask now orders JSON keys by default to not trash HTTP caches due todifferent hash seeds between different workers.
• Added appcontext_pushed and appcontext_popped signals.
• The builtin run method now takes the SERVER_NAME into account whenpicking the default port to run on.
• Added flask.request.get_json() as a replacement for the oldflask.request.json property.

Version 0.9¶

Released on July 1st 2012, codename Campari.

• The flask.Request.on_json_loading_failed() now returns a JSON formattedresponse by default.
• The flask.url_for() function now can generate anchors to thegenerated links.
• The flask.url_for() function now can also explicitly generateURL rules specific to a given HTTP method.
• Logger now only returns the debug log setting if it was not setexplicitly.
• Unregister a circular dependency between the WSGI environment andthe request object when shutting down the request. This means thatenviron werkzeug.request will be None after the response wasreturned to the WSGI server but has the advantage that the garbagecollector is not needed on CPython to tear down the request unlessthe user created circular dependencies themselves.
• Session is now stored after callbacks so that if the session payloadis stored in the session you can still modify it in an afterrequest callback.
• The flask.Flask class will avoid importing the provided import nameif it can (the required first parameter), to benefit tools which build Flaskinstances programmatically. The Flask class will fall back to using importon systems with custom module hooks, e.g. Google App Engine, or when theimport name is inside a zip archive (usually a .egg) prior to Python 2.7.
• Blueprints now have a decorator to add custom template filters applicationwide, flask.Blueprint.app_template_filter().
• The Flask and Blueprint classes now have a non-decorator method for addingcustom template filters application wide,flask.Flask.add_template_filter() andflask.Blueprint.add_app_template_filter().
• The flask.get_flashed_messages() function now allows rendering flashedmessage categories in separate blocks, through a category_filterargument.
• The flask.Flask.run() method now accepts None for host and _port_arguments, using default values when None. This allows for calling runusing configuration values, e.g. app.run(app.config.get('MYHOST'),
  app.config.get('MYPORT')), with proper behavior whether or not a configfile is provided.
• The flask.render_template() method now accepts a either an iterable oftemplate names or a single template name. Previously, it only accepted asingle template name. On an iterable, the first template found is rendered.
• Added flask.Flask.app_context() which works very similar to therequest context but only provides access to the current application. Thisalso adds support for URL generation without an active request context.
• View functions can now return a tuple with the first instance being aninstance of flask.Response. This allows for returningjsonify(error="error msg"), 400 from a view function.
• Flask and Blueprint now provide aget_send_file_max_age() hook for subclasses to overridebehavior of serving static files from Flask when usingflask.Flask.send_static_file() (used for the default static filehandler) and sendfile(). This hook is provided afilename, which for example allows changing cache controls by file extension.The default max-age for _send_file and static files can be configuredthrough a new SENDFILE_MAX_AGE_DEFAULT configuration variable, which isused in the default _get_send_file_max_age implementation.
• Fixed an assumption in sessions implementation which could break messageflashing on sessions implementations which use external storage.
• Changed the behavior of tuple return values from functions. They are nolonger arguments to the response object, they now have a defined meaning.
• Added flask.Flask.request_globals_class to allow a specific class tobe used on creation of the g instance of each request.
• Added required_methods attribute to view functions to force-add methodson registration.
• Added flask.after_this_request().
• Added flask.stream_with_context() and the ability to push contextsmultiple times without producing unexpected behavior.

Version 0.8.1¶

Bugfix release, released on July 1st 2012

• Fixed an issue with the undocumented flask.session module to notwork properly on Python 2.5. It should not be used but did causesome problems for package managers.

Version 0.8¶

Released on September 29th 2011, codename Rakija

• Refactored session support into a session interface so thatthe implementation of the sessions can be changed withouthaving to override the Flask class.
• Empty session cookies are now deleted properly automatically.
• View functions can now opt out of getting the automaticOPTIONS implementation.
• HTTP exceptions and Bad Request errors can now be trapped so that theyshow up normally in the traceback.
• Flask in debug mode is now detecting some common problems and tries towarn you about them.
• Flask in debug mode will now complain with an assertion error if a viewwas attached after the first request was handled. This gives earlierfeedback when users forget to import view code ahead of time.
• Added the ability to register callbacks that are only triggered once atthe beginning of the first request. (Flask.before_first_request())
• Malformed JSON data will now trigger a bad request HTTP exception insteadof a value error which usually would result in a 500 internal servererror if not handled. This is a backwards incompatible change.
• Applications now not only have a root path where the resources and modulesare located but also an instance path which is the designated place todrop files that are modified at runtime (uploads etc.). Also this isconceptually only instance depending and outside version control so it’sthe perfect place to put configuration files etc. For more informationsee 实例文件夹.
• Added the APPLICATION_ROOT configuration variable.
• Implemented session_transaction() toeasily modify sessions from the test environment.
• Refactored test client internally. The APPLICATION_ROOT configurationvariable as well as SERVER_NAME are now properly used by the test clientas defaults.
• Added flask.views.View.decorators to support simpler decorating ofpluggable (class-based) views.
• Fixed an issue where the test client if used with the “with” statement did nottrigger 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 flask.ext package to import extensions from.
• The context preservation on exceptions is now an integral component ofFlask itself and no longer of the test client. This cleaned up someinternal logic and lowers the odds of runaway request contexts in unittests.

Version 0.7.3¶

Bugfix release, release date to be decided

• Fixed the Jinja2 environment’s list_templates method not returning thecorrect names when blueprints or modules were involved.

Version 0.7.2¶

Bugfix release, released on July 6th 2011

• Fixed an issue with URL processors not properly working onblueprints.

Version 0.7.1¶

Bugfix release, released on June 29th 2011

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

Version 0.7¶

Released on June 28th 2011, codename Grappa

• Added make_default_options_response()which can be used by subclasses to alter the defaultbehavior for OPTIONS responses.
• Unbound locals now raise a proper RuntimeError insteadof an AttributeError.
• Mimetype guessing and etag support based on file objects is nowdeprecated for flask.send_file() because it was unreliable.Pass filenames instead or attach your own etags and provide aproper mimetype by hand.
• Static file handling for modules now requires the name of thestatic folder to be supplied explicitly. The previous autodetectionwas not reliable and caused issues on Google’s App Engine. Until1.0 the old behavior will continue to work but issue dependencywarnings.
• fixed a problem for Flask to run on jython.
• added a PROPAGATE_EXCEPTIONS configuration variable that can beused to flip the setting of exception propagation which previouslywas linked to DEBUG alone and is now linked to either DEBUG orTESTING.
• Flask no longer internally depends on rules being added through theadd_url_rule function and can now also accept regular werkzeugrules added to the url map.
• Added an endpoint method to the flask application object whichallows one to register a callback to an arbitrary endpoint witha decorator.
• Use Last-Modified for static file sending instead of Date whichwas incorrectly introduced in 0.6.
• Added create_jinja_loader to override the loader creation process.
• Implemented a silent flag for config.from_pyfile.
• Added teardown_request decorator, for functions that should run at the endof a request regardless of whether an exception occurred. Also the behaviorfor after_request was changed. It’s now no longer executed when an exceptionis raised. See Upgrading to new Teardown Handling
• Implemented flask.has_request_context()
• Deprecated init_jinja_globals. Override thecreate_jinja_environment() method instead toachieve the same functionality.
• Added flask.safe_join()
• The automatic JSON request data unpacking now looks at the charsetmimetype parameter.
• Don’t modify the session on flask.get_flashed_messages() if thereare no messages in the session.
• before_request handlers are now able to abort requests with errors.
• it is not possible to define user exception handlers. That way you canprovide custom error messages from a central hub for certain errors thatmight occur during request processing (for instance database connectionerrors, timeouts from remote resources etc.).
• Blueprints can provide blueprint specific error handlers.
• Implemented generic 可插拨视图 (class-based views).

Version 0.6.1¶

Bugfix release, released on December 31st 2010

• Fixed an issue where the default OPTIONS response wasnot exposing all valid methods in the Allow header.
• Jinja2 template loading syntax now allows “./” in front ofa template load path. Previously this caused issues withmodule setups.
• Fixed an issue where the subdomain setting for modules wasignored for the static folder.
• Fixed a security problem that allowed clients to download arbitrary filesif the host server was a windows based operating system and the clientuses backslashes to escape the directory the files where exposed from.

Version 0.6¶

Released on July 27th 2010, codename Whisky

• after request functions are now called in reverse order ofregistration.
• OPTIONS is now automatically implemented by Flask unless theapplication explicitly 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 folderfor the module. This was implemented to aid GAE which willremove the static folder if it’s part of a mapping in the .ymlfile.
• the config is now available in the templatesas config.
• context processors will no longer override values passed directlyto the render function.
• added the ability to limit the incoming request data with thenew MAX_CONTENT_LENGTH configuration value.
• the endpoint for the flask.Module.add_url_rule() methodis now optional to be consistent with the function of thesame name on the application object.
• added a flask.make_response() function that simplifiescreating response object instances in views.
• added signalling support based on blinker. This feature is currentlyoptional and supposed to be used by extensions and applications. Ifyou want to use it, make sure to have blinker installed.
• refactored the way URL adapters are created. This process is nowfully customizable with the create_url_adapter()method.
• modules can now register for a subdomain instead of just an URLprefix. This makes it possible to bind a whole module to aconfigurable subdomain.

Version 0.5.2¶

Bugfix Release, released on July 15th 2010

• fixed another issue with loading templates from directories whenmodules were used.

Version 0.5.1¶

Bugfix Release, released on July 6th 2010

• fixes an issue with template loading from directories when moduleswhere used.

Version 0.5¶

Released on July 6th 2010, codename Calvados

• fixed a bug with subdomains that was caused by the inability tospecify the server name. The server name can now be set withthe SERVER_NAME config key. This key is now also used to setthe session cookie cross-subdomain wide.
• autoescaping is no longer active for all templates. Instead itis only active for .html, .htm, .xml and .xhtml.Inside templates this behavior can be changed with theautoescape tag.
• refactored Flask internally. It now consists of more than asingle file.
• flask.send_file() now emits etags and has the ability todo conditional responses builtin.
• (temporarily) dropped support for zipped applications. This was ararely used feature and led to some confusing behavior.
• added support for per-package template and static-file directories.
• removed support for create_jinja_loader which is no longer usedin 0.5 due to the improved module support.
• added a helper function to expose files from any directory.

Version 0.4¶

Released on June 18th 2010, codename Rakia

• added the ability to register application wide error handlersfrom modules.
• after_request() handlers are now also invokedif the request dies with an exception and an error handling pagekicks in.
• test client has not the ability to preserve the request contextfor a little longer. This can also be used to trigger customrequests that do not pop the request stack for testing.
• because the Python standard library caches loggers, the name ofthe 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.

Version 0.3.1¶

Bugfix release, released on May 28th 2010

• fixed a error reporting bug with flask.Config.from_envvar()
• removed some unused code from flask
• release does no longer include development leftover files (.gitfolder for themes, built documentation in zip and pdf file andsome .pyc files)

Version 0.3¶

Released on May 28th 2010, codename Schnaps

• added support for categories for flashed messages.
• the application now configures a logging.Handler and willlog request handling exceptions to that logger when not in debugmode. This makes it possible to receive mails on server errorsfor example.
• added support for context binding that does not require the use ofthe with statement for playing in the console.
• the request context is now available within the with statement makingit possible to further push the request context or pop it.
• added support for configurations.

Version 0.2¶

Released on May 12th 2010, codename Jägermeister

• various bugfixes
• integrated JSON support
• added get_template_attribute() helper function.
• add_url_rule() can now also register aview function.
• refactored internal request dispatching.
• server listens on 127.0.0.1 by default now to fix issues with chrome.
• added external URL support.
• added support for send_file()
• module support and internal request handling refactoringto better support pluggable applications.
• sessions can be set to be permanent now on a per-session basis.
• better error reporting on missing secret keys.
• added support for Google Appengine.

Version 0.1¶

First public preview release.

原文: https://dormousehole.readthedocs.io/en/latest/changelog.html