Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Initial Update #3

Closed
wants to merge 4 commits into from
Closed

Initial Update #3

wants to merge 4 commits into from

Conversation

pyup-bot
Copy link
Collaborator

This is my first visit to this fine repo so I have bundled all updates in a single pull request to make things easier for you to merge.

Close this pull request and delete the branch if you want me to start with single pull requests right away

Here's the executive summary:

Updates

Here's a list of all the updates bundled in this pull request. I've added some links to make it easier for you to find all the information you need.

flask 0.12.1 » 0.12.1 PyPI | Changelog | Repo
blinker 1.4 » 1.4 PyPI | Changelog | Homepage | Docs
flask-wtf 0.8.2 » 0.14.2 PyPI | Changelog | Repo | Docs
wtforms-json 0.1.2 » 0.3.1 PyPI | Changelog | Repo

Changelogs

flask -> 0.12.1

0.12.1


Bugfix release, released on March 31st 2017

  • Prevent flask run from showing a NoAppException when an ImportError occurs
    within 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 for
    app.run. 2109, 2152
  • Call ctx.auto_pop with the exception object instead of None, in the
    event that a BaseException such as KeyboardInterrupt is raised in a
    request handler.

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_file
    has been removed, as per issue 104. See pull request 1849.
  • Mimetype guessing in send_file now fails loudly and doesn't fall back to
    application/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 returning
    a Internal Server Error (pull request 2006).
  • Correctly invoke response handlers for both regular request dispatching as
    well 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 be
    directly set, instead of per client.get.

0.11.2


Bugfix release, unreleased

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

0.11.1


Bugfix release, released on June 7th 2016.

  • Fixed a bug that prevented FLASK_APP=foobar/__init__.py from working. See
    pull request 1872.

0.11


Released on May 29th 2016, codename Absinthe.

  • Added support to serializing top-level arrays to :func:flask.jsonify. This
    introduces a security risk in ancient browsers. See
    :ref:json-security for details.
  • Added before_render_template signal.
  • Added **kwargs to :meth:flask.Test.test_client to support passing
    additional keyword arguments to the constructor of
    :attr:flask.Flask.test_client_class.
  • Added SESSION_REFRESH_EACH_REQUEST config key that controls the
    set-cookie behavior. If set to True a permanent session will be
    refreshed each request and get their lifetime extended, if set to
    False it will only be modified if the session actually modifies.
    Non permanent sessions are not affected by this and will always
    expire 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 :meth:flask.Config.from_json.
  • Added :attr:flask.Flask.config_class.
  • Added :meth:flask.Config.get_namespace.
  • Templates are no longer automatically reloaded outside of debug mode. This
    can 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 namespace
    packages.
  • Added :command:flask and the flask.cli module to start the local
    debug server through the click CLI system. This is recommended over the old
    flask.run() method as it works faster and more reliable due to a
    different design and also replaces Flask-Script.
  • Error handlers that match specific classes are now checked first,
    thereby allowing catching exceptions that are subclasses of HTTP
    exceptions (in werkzeug.exceptions). This makes it possible
    for an extension author to create exceptions that will by default
    result in the HTTP error of their choosing, but may be caught with
    a custom error handler if desired.
  • Added :meth:flask.Config.from_mapping.
  • Flask will now log by default even if debug is disabled. The log format is
    now hardcoded but the default log handling can be disabled through the
    LOGGER_HANDLER_POLICY configuration key.
  • Removed deprecated module functionality.
  • Added the EXPLAIN_TEMPLATE_LOADING config flag which when enabled will
    instruct Flask to explain how it locates templates. This should help
    users debug when the wrong templates are loaded.
  • Enforce blueprint handling in the order they were registered for template
    loading.
  • 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 removing
    unnecessary white space included by default after separators.
  • JSON responses are now terminated with a newline character, because it is a
    convention that UNIX text files end with a newline and some clients don't
    deal well when this newline is missing. See
    Add JSONIFY_END_WITH_NEWLINE config variable pallets/flask#1262 -- this came up originally as a
    part of https://github.com/kennethreitz/httpbin/issues/168
  • The automatically provided OPTIONS method is now correctly disabled if
    the user registered an overriding rule with the lowercase-version
    options (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 teardown
    handlers (pull request 1393).
  • Allow custom Jinja environment subclasses (pull request 1422).
  • 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 on
    the server OS (pull request 1763).
  • Added the JSONIFY_MIMETYPE configuration variable (pull request 1728).
  • Exceptions during teardown handling will no longer leave bad application
    contexts lingering around.

0.10.2


(bugfix release, release date to be announced)

  • Fixed broken test_appcontext_signals() test case.
  • Raise an :exc:AttributeError in :func:flask.helpers.find_package with a
    useful message explaining why it is raised when a PEP 302 import hook is used
    without an is_package() method.
  • Fixed an issue causing exceptions raised before entering a request or app
    context to be passed to teardown handlers.
  • Fixed an issue with query parameters getting removed from requests in
    the 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 path
    correctly.
  • Changed logic of before first request handlers to flip the flag after
    invoking. This will allow some uses that are potentially dangerous but
    should probably be permitted.
  • Fixed Python 3 bug when a handler from app.url_build_error_handlers
    reraises the BuildError.

0.10.1


(bugfix release, released on June 14th 2013)

  • Fixed an issue where |tojson was not quoting single quotes which
    made the filter not work properly in HTML attributes. Now it's
    possible to use that filter in single quoted attributes. This should
    make using that filter with angular.js easier.
  • 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.

0.10


Released on June 13th 2013, codename Limoncello.

  • Changed default cookie serialization format from pickle to JSON to
    limit the impact an attacker can do if the secret key leaks. See
    :ref:upgrading-to-010 for more information.
  • Added template_test methods in addition to the already existing
    template_filter method family.
  • Added template_global methods in addition to the already existing
    template_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 was
    allowed due to the different escaping behavior.
  • Flask will now raise an error if you attempt to register a new function
    on an already used endpoint.
  • Added wrapper module around simplejson and added default serialization
    of datetime objects. This allows much easier customization of how
    JSON is handled by Flask or any Flask extension.
  • Removed deprecated internal flask.session module alias. Use
    flask.sessions instead to get the session module. This is not to
    be confused with flask.session the session proxy.
  • Templates can now be rendered without request context. The behavior is
    slightly different as the request, session and g objects
    will not be available and blueprint's context processors are not
    called.
  • The config object is now available to the template as a real global and
    not through a context processor which makes it available even in imported
    templates by default.
  • Added an option to generate non-ascii encoded JSON which should result
    in less bytes being transmitted over the network. It's disabled by
    default to not cause confusion with existing libraries that might expect
    flask.json.dumps to return bytestrings by default.
  • flask.g is now stored on the app context instead of the request
    context.
  • flask.g now gained a get() method for not erroring out on non
    existing items.
  • flask.g now can be used with the in operator to see what's defined
    and it now is iterable and will yield all attributes stored.
  • flask.Flask.request_globals_class got renamed to
    flask.Flask.app_ctx_globals_class which is a better name to what it
    does since 0.10.
  • request, session and g are now also added as proxies to the template
    context which makes them available in imported templates. One has to be
    very careful with those though because usage outside of macros might
    cause caching.
  • Flask will no longer invoke the wrong error handlers if a proxy
    exception is passed through.
  • Added a workaround for chrome's cookies in localhost not working
    as intended with domain names.
  • Changed logic for picking defaults for cookie values from sessions
    to work better with Google Chrome.
  • Added message_flashed signal that simplifies flashing testing.
  • Added support for copying of request contexts for better working with
    greenlets.
  • Removed custom JSON HTTP exception subclasses. If you were relying on them
    you can reintroduce them again yourself trivially. Using them however is
    strongly discouraged as the interface was flawed.
  • Python requirements changed: requiring Python 2.6 or 2.7 now to prepare
    for Python 3.3 port.
  • Changed how the teardown system is informed about exceptions. This is now
    more reliable in case something handles an exception halfway through
    the error handling process.
  • Request context preservation in debug mode now keeps the exception
    information around which means that teardown handlers are able to
    distinguish error from success cases.
  • Added the JSONIFY_PRETTYPRINT_REGULAR configuration variable.
  • Flask now orders JSON keys by default to not trash HTTP caches due to
    different hash seeds between different workers.
  • Added appcontext_pushed and appcontext_popped signals.
  • The builtin run method now takes the SERVER_NAME into account when
    picking the default port to run on.
  • Added flask.request.get_json() as a replacement for the old
    flask.request.json property.

0.9


Released on July 1st 2012, codename Campari.

  • The :func:flask.Request.on_json_loading_failed now returns a JSON formatted
    response by default.
  • The :func:flask.url_for function now can generate anchors to the
    generated links.
  • The :func:flask.url_for function now can also explicitly generate
    URL rules specific to a given HTTP method.
  • Logger now only returns the debug log setting if it was not set
    explicitly.
  • Unregister a circular dependency between the WSGI environment and
    the request object when shutting down the request. This means that
    environ werkzeug.request will be None after the response was
    returned to the WSGI server but has the advantage that the garbage
    collector is not needed on CPython to tear down the request unless
    the user created circular dependencies themselves.
  • Session is now stored after callbacks so that if the session payload
    is stored in the session you can still modify it in an after
    request callback.
  • The :class:flask.Flask class will avoid importing the provided import name
    if it can (the required first parameter), to benefit tools which build Flask
    instances programmatically. The Flask class will fall back to using import
    on systems with custom module hooks, e.g. Google App Engine, or when the
    import name is inside a zip archive (usually a .egg) prior to Python 2.7.
  • Blueprints now have a decorator to add custom template filters application
    wide, :meth:flask.Blueprint.app_template_filter.
  • The Flask and Blueprint classes now have a non-decorator method for adding
    custom template filters application wide,
    :meth:flask.Flask.add_template_filter and
    :meth:flask.Blueprint.add_app_template_filter.
  • The :func:flask.get_flashed_messages function now allows rendering flashed
    message categories in separate blocks, through a category_filter
    argument.
  • The :meth:flask.Flask.run method now accepts None for host and port
    arguments, using default values when None. This allows for calling run
    using configuration values, e.g. app.run(app.config.get('MYHOST'), app.config.get('MYPORT')), with proper behavior whether or not a config
    file is provided.
  • The :meth:flask.render_template method now accepts a either an iterable of
    template names or a single template name. Previously, it only accepted a
    single template name. On an iterable, the first template found is rendered.
  • Added :meth:flask.Flask.app_context which works very similar to the
    request context but only provides access to the current application. This
    also adds support for URL generation without an active request context.
  • View functions can now return a tuple with the first instance being an
    instance of :class:flask.Response. This allows for returning
    jsonify(error="error msg"), 400 from a view function.
  • :class:~flask.Flask and :class:~flask.Blueprint now provide a
    :meth:~flask.Flask.get_send_file_max_age hook for subclasses to override
    behavior of serving static files from Flask when using
    :meth:flask.Flask.send_static_file (used for the default static file
    handler) and :func:~flask.helpers.send_file. This hook is provided a
    filename, which for example allows changing cache controls by file extension.
    The default max-age for send_file and static files can be configured
    through a new SEND_FILE_MAX_AGE_DEFAULT configuration variable, which is
    used in the default get_send_file_max_age implementation.
  • 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.

0.8.1


Bugfix release, released on July 1st 2012

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

0.8


Released on September 29th 2011, codename Rakija

  • 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 instance path which is the designated place to
    drop files that are modified at runtime (uploads etc.). Also this is
    conceptually 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 extensions 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.

0.7.3


Bugfix release, release date to be decided

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

0.7.2


Bugfix release, released on July 6th 2011

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

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.

0.7


Released on June 28th 2011, codename Grappa

  • Added :meth:~flask.Flask.make_default_options_response
    which can be used by subclasses to alter the default
    behavior for OPTIONS responses.
  • Unbound locals now raise a proper :exc:RuntimeError instead
    of an :exc:AttributeError.
  • Mimetype guessing and etag support based on file objects is now
    deprecated for :func:flask.send_file because it was unreliable.
    Pass filenames instead or attach your own etags and provide a
    proper mimetype by hand.
  • Static file handling for modules now requires the name of the
    static folder to be supplied explicitly. The previous autodetection
    was not reliable and caused issues on Google's App Engine. Until
    1.0 the old behavior will continue to work but issue dependency
    warnings.
  • fixed a problem for Flask to run on jython.
  • added a PROPAGATE_EXCEPTIONS configuration variable that can be
    used to flip the setting of exception propagation which previously
    was linked to DEBUG alone and is now linked to either DEBUG or
    TESTING.
  • Flask no longer internally depends on rules being added through the
    add_url_rule function and can now also accept regular werkzeug
    rules added to the url map.
  • Added an endpoint method to the flask application object which
    allows one to register a callback to an arbitrary endpoint with
    a decorator.
  • Use Last-Modified for static file sending instead of Date which
    was 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 end
    of a request regardless of whether an exception occurred. Also the behavior
    for after_request was changed. It's now no longer executed when an exception
    is raised. See :ref:upgrading-to-new-teardown-handling
  • Implemented :func:flask.has_request_context
  • Deprecated init_jinja_globals. Override the
    :meth:~flask.Flask.create_jinja_environment method instead to
    achieve the same functionality.
  • Added :func:flask.safe_join
  • The automatic JSON request data unpacking now looks at the charset
    mimetype parameter.
  • Don't modify the session on :func:flask.get_flashed_messages if there
    are 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 can
    provide custom error messages from a central hub for certain errors that
    might occur during request processing (for instance database connection
    errors, timeouts from remote resources etc.).
  • Blueprints can provide blueprint specific error handlers.
  • Implemented generic :ref:views (class-based views).

0.6.1


Bugfix release, released on December 31st 2010

  • 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.

0.6


Released on July 27th 2010, codename Whisky

  • after request functions are now called in reverse order of
    registration.
  • OPTIONS is now automatically implemented by Flask unless the
    application 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 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.

.. _blinker: https://pypi.python.org/pypi/blinker

0.5.2


Bugfix Release, released on July 15th 2010

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

0.5.1


Bugfix Release, released on July 6th 2010

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

0.5


Released on July 6th 2010, codename Calvados

  • fixed a bug with subdomains that was caused by the inability to
    specify the server name. The server name can now be set with
    the SERVER_NAME config key. This key is now also used to set
    the session cookie cross-subdomain wide.
  • autoescaping is no longer active for all templates. Instead it
    is only active for .html, .htm, .xml and .xhtml.
    Inside templates this behavior can be changed with the
    autoescape tag.
  • refactored Flask internally. It now consists of more than a
    single file.
  • :func:flask.send_file now emits etags and has the ability to
    do conditional responses builtin.
  • (temporarily) dropped support for zipped applications. This was a
    rarely 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 used
    in 0.5 due to the improved module support.
  • added a helper function to expose files from any directory.

0.4


Released on June 18th 2010, codename Rakia

  • 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.

0.3.1


Bugfix release, released on May 28th 2010

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

0.3


Released on May 28th 2010, codename Schnaps

  • added support for categories for flashed messages.
  • the application now configures a :class:logging.Handler and will
    log request handling exceptions to that logger when not in debug
    mode. This makes it possible to receive mails on server errors
    for example.
  • added support for context binding that does not require the use of
    the with statement for playing in the console.
  • the request context is now available within the with statement making
    it possible to further push the request context or pop it.
  • added support for configurations.

0.2


Released on May 12th 2010, codename Jägermeister

  • various bugfixes
  • integrated JSON support
  • added :func:~flask.get_template_attribute helper function.
  • :meth:~flask.Flask.add_url_rule can now also register a
    view 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 :func:~flask.send_file
  • module support and internal request handling refactoring
    to 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.

0.1


First public preview release.

blinker -> 1.4

1.4


Released July 23, 2015

  • Verified Python 3.4 support (no changes needed)
  • Additional bookkeeping cleanup for non-ANY connections at disconnect
    time.
  • Added Signal._cleanup_bookeeping() to prune stale bookkeeping on
    demand

1.3


Released July 3, 2013

  • The global signal stash behind blinker.signal() is now backed by a
    regular name-to-Signal dictionary. Previously, weak references were
    held in the mapping and ephermal usage in code like
    signal('foo').connect(...) could have surprising program behavior
    depending on import order of modules.
  • blinker.Namespace is now built on a regular dict. Use
    blinker.WeakNamespace for the older, weak-referencing behavior.
  • Signal.connect('text-sender') uses an alterate hashing strategy to
    avoid sharp edges in text identity.

1.2


Released October 26, 2011

  • Added Signal.receiver_connected and
    Signal.receiver_disconnected per-Signal signals.
  • Deprecated the global 'receiver_connected' signal.
  • Verified Python 3.2 support (no changes needed!)

1.1


Released July 21, 2010

  • Added signal.connect_via(sender) decorator
  • Added signal.connected_to shorthand name for the
    temporarily_connected_to context manager.

1.0


Released March 28, 2010

  • Python 3.0 and 3.1 compatibility

0.9


Released February 26, 2010

  • Added Signal.temporarily_connected_to context manager
  • Docs! Sphinx docs, project web site.

0.8


Released February 14, 2010

  • Initial release
  • Extracted from flatland.util.signals
  • Added Python 2.4 compatibility
  • Added nearly functional Python 3.1 compatibility (everything except
    connecting to instance methods seems to work.)

flask-wtf 0.8.2 -> 0.14.2

0.14.2


Released 2017-01-10

  • Fix bug where FlaskForm assumed meta argument was not None if it
    was passed. (278_)

.. _278: wtforms/flask-wtf#278

0.14.1


Released 2017-01-10

  • Fix bug where the file validators would incorrectly identify an empty file as
    valid data. (276, 277)
  • FileField is no longer deprecated. The data is checked during
    processing and only set if it's a valid file.
  • has_file is deprecated; it's now equivalent to bool(field.data).
  • FileRequired and FileAllowed work with both the Flask-WTF and
    WTForms FileField classes.
  • The Optional validator now works with FileField.

.. _276: wtforms/flask-wtf#276
.. _277: wtforms/flask-wtf#277

0.14


Released 2017-01-06

  • Use itsdangerous to sign CSRF tokens and check expiration instead of doing it
    ourselves. (264_)
  • All tokens are URL safe, removing the url_safe parameter from
    generate_csrf. (206_)
  • All tokens store a timestamp, which is checked in validate_csrf. The
    time_limit parameter of generate_csrf is removed.
  • Remove the app attribute from CsrfProtect, use current_app.
    (264_)
  • CsrfProtect protects the DELETE method by default. (264_)
  • The same CSRF token is generated for the lifetime of a request. It is exposed
    as request.csrf_token for use during testing. (227, 264)
  • CsrfProtect.error_handler is deprecated. (264_)
  • Handlers that return a response work in addition to those that raise an
    error. The behavior was not clear in previous docs.
  • (200, 209, 243, 252)
  • Use Form.Meta instead of deprecated SecureForm for CSRF (and
    everything else). (216, 271)
  • csrf_enabled parameter is still recognized but deprecated. All other
    attributes and methods from SecureForm are removed. (271_)
  • Provide WTF_CSRF_FIELD_NAME to configure the name of the CSRF token.
    (271_)
  • validate_csrf raises wtforms.ValidationError with specific messages
    instead of returning True or False. This breaks anything that was
    calling the method directly. (239, 271)
  • CSRF errors are logged as well as raised. (239_)
  • CsrfProtect is renamed to CSRFProtect. A deprecation warning is issued
    when using the old name. CsrfError is renamed to CSRFError without
    deprecation. (271_)
  • FileField is deprecated because it no longer provides functionality over
    the provided validators. Use wtforms.FileField directly. (272_)

.. _200: wtforms/flask-wtf#200
.. _209: wtforms/flask-wtf#209
.. _216: wtforms/flask-wtf#216
.. _227: wtforms/flask-wtf#227
.. _239: wtforms/flask-wtf#239
.. _243: wtforms/flask-wtf#243
.. _252: wtforms/flask-wtf#252
.. _264: wtforms/flask-wtf#264
.. _271: wtforms/flask-wtf#271
.. _272: wtforms/flask-wtf#272

0.13.1


Released 2016/10/6

  • Deprecation warning for Form is shown during __init__ instead of immediately when subclassing. (262_)
  • Don't use pkg_resources to get version, for compatibility with GAE. (261_)

.. _261: wtforms/flask-wtf#261
.. _262: wtforms/flask-wtf#262

0.13


Released 2016/09/29

  • Form is renamed to FlaskForm in order to avoid name collision with WTForms's base class. Using Form will show a deprecation warning. (250_)
  • hidden_tag no longer wraps the hidden inputs in a hidden div. This is valid HTML5 and any modern HTML parser will behave correctly. (217, 193)
  • flask_wtf.html5 is deprecated. Import directly from wtforms.fields.html5. (251_)
  • is_submitted is true for PATCH and DELETE in addition to POST and PUT. (187_)
  • generate_csrf takes a token_key parameter to specify the key stored in the session. (206_)
  • generate_csrf takes a url_safe parameter to allow the token to be used in URLs. (206_)
  • form.data can be accessed multiple times without raising an exception. (248_)
  • File extension with multiple parts (.tar.gz) can be used in the FileAllowed validator. (201_)

.. _187: wtforms/flask-wtf#187
.. _193: wtforms/flask-wtf#193
.. _201: wtforms/flask-wtf#201
.. _206: wtforms/flask-wtf#206
.. _217: wtforms/flask-wtf#217
.. _248: wtforms/flask-wtf#248
.. _250: wtforms/flask-wtf#250
.. _251: wtforms/flask-wtf#251

0.12


Released 2015/07/09

  • Abstract protect_csrf() into a separate method
  • Update reCAPTCHA configuration
  • Fix reCAPTCHA error handle

0.11


Released 2015/01/21

  • Use the new reCAPTCHA API via 164_.

.. _164: wtforms/flask-wtf#164

0.10.3


Released 2014/11/16

  • Add configuration: WTF_CSRF_HEADERS via 159_.
  • Support customize hidden tags via 150_.
  • And many more bug fixes

.. _150: wtforms/flask-wtf#150
.. _159: wtforms/flask-wtf#159

0.10.2


Released 2014/09/03

  • Update translation for reCaptcha via 146_.

.. _146: wtforms/flask-wtf#146

0.10.1


Released 2014/08/26

  • Update RECAPTCHA API SERVER URL via 145_.
  • Update requirement Werkzeug>=0.9.5
  • Fix CsrfProtect exempt for blueprints via 143_.

.. _145: wtforms/flask-wtf#145
.. _143: wtforms/flask-wtf#143

0.10.0


Released 2014/07/16

  • Add configuration: WTF_CSRF_METHODS
  • Support WTForms 2.0 now
  • Fix csrf validation without time limit (time_limit=False)
  • CSRF exempt supports blueprint 111_.

.. _111: wtforms/flask-wtf#111

0.9.5


Released 2014/03/21

  • csrf_token for all template types 112_.
  • Make FileRequired a subclass of InputRequired 108_.

.. _108: wtforms/flask-wtf#108
.. _112: wtforms/flask-wtf#112

0.9.4


Released 2013/12/20

  • Bugfix for csrf module when form has a prefix
  • Compatible support for wtforms2
  • Remove file API for FileField

0.9.3


Released 2013/10/02

  • Fix validation of recaptcha when app in testing mode 89_.
  • Bugfix for csrf module 91_

.. _89: wtforms/flask-wtf#89
.. _91: wtforms/flask-wtf#91

0.9.2


Released 2013/9/11

  • Upgrade wtforms to 1.0.5.
  • No lazy string for i18n 77_.
  • No DateInput widget in html5 81_.
  • PUT and PATCH for CSRF 86_.

.. _77: wtforms/flask-wtf#77
.. _81: wtforms/flask-wtf#81
.. _86: wtforms/flask-wtf#86

0.9.1


Released 2013/8/21

This is a patch version for backward compitable for Flask<0.10 82_.

.. _82: wtforms/flask-wtf#82

0.9.0


Released 2013/8/15

  • Add i18n support (issue 65)
  • Use default html5 widgets and fields provided by wtforms
  • Python 3.3+ support
  • Redesign form, replace SessionSecureForm
  • CSRF protection solution
  • Drop wtforms imports
  • Fix recaptcha i18n support
  • Fix recaptcha validator for python 3
  • More test cases, it's 90%+ coverage now
  • Redesign documentation

0.8.4


Released 2013/3/28

  • Recaptcha Validator now returns provided message (issue 66)
  • Minor doc fixes
  • Fixed issue with tests barking because of nose/multiprocessing issue.

0.8.3


Released 2013/3/13

  • Update documentation to indicate pending deprecation of WTForms namespace
    facade
  • PEP8 fixes (issue 64)
  • Fix Recaptcha widget (issue 49)

wtforms-json 0.1.2 -> 0.3.1

0.3.1

^^^^^^^^^^^^^^^^^^

  • Fixed default value handling for StringField (49, pull request courtesy noirbizarre)
  • Added py36 to test matrix

0.3.0

^^^^^^^^^^^^^^^^^^

  • Added support for WTForms 3.0
  • Dropped Python 2.6 support

0.2.10

^^^^^^^^^^^^^^^^^^

  • Fixed process_formdata support for python3
  • Added flake8 and isort checks

0.2.9

^^^^^^^^^^^^^^^^^^

  • Fixed inheritance handling with FieldLists and FormFields

0.2.8

^^^^^^^^^^^^^^^^^^

  • Fixed falsy boolean value handling

0.2.7

^^^^^^^^^^^^^^^^^^

  • Only flatten dict if field is an instance of FormField

0.2.6

^^^^^^^^^^^^^^^^^^

  • Made skip_unknown_keys=True prevent raising errors from keys that exist in
    form class but are not form fields

0.2.5

^^^^^^^^^^^^^^^^^^

  • Fixed skip_unknown_keys option passing from from_json to
    flatten_json (17)

0.2.4

^^^^^^^^^^^^^^^^^^

  • Fixed object value setting in from_json
  • Prepared support for WTForms 2.0

0.2.3

^^^^^^^^^^^^^^^^^^

  • Added support for QuerySelectField and QuerySelectMultipleField

0.2.2

^^^^^^^^^^^^^^^^^^

  • Configurable unknown json key handling

0.2.1

^^^^^^^^^^^^^^^^^^

  • Custom SelectField support

0.2.0

^^^^^^^^^^^^^^^^^^

  • Rewritten flatten_json (now supports SelectMultipleFields)

0.1.5

^^^^^^^^^^^^^^^^^^

  • Added enhanced unicode coercion
  • Package six added to requirements

0.1.4

^^^^^^^^^^^^^^^^^^

  • Updated WTForms requirements

0.1.3

^^^^^^^^^^^^^^^^^^

  • Fixed 'First example' in docs

Once you have closed this pull request, I'll create seperate pull requests for every update as soon as I find them.

That's it for now!

Happy merging! 🤖

@gregorynicholas gregorynicholas deleted the pyup-initial-update branch April 11, 2017 13:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants