Release v19.12.0 (#1740)

* Bumping up version from 19.9.0 to 19.12.0

* Pipfile crud removed

changelogs/1691.doc.rst

@@ -1,4 +0,0 @@
-Move docs from RST to MD
-
-Moved all docs from markdown to restructured text like the rest of the docs to unify the scheme and make it easier in
-the future to update documentation.

changelogs/1704.doc.rst

@@ -1,3 +0,0 @@
-Fix documentation for `get` and `getlist` of the `request.args`
-
-Add additional example for showing the usage of `getlist` and fix the documentation string for `request.args` behavior

changelogs/1707.bugfix.rst

@@ -1,4 +0,0 @@
-Fix `url_for` behavior with missing SERVER_NAME
-
-If the `SERVER_NAME` was missing in the `app.config` entity, the `url_for` on the `request` and  `app` were failing
-due to an `AttributeError`. This fix makes the availability of `SERVER_NAME` on our `app.config` an optional behavior.

changelogs/37.bugfix.rst

@@ -1,11 +0,0 @@
-Fix blueprint middleware application
-
-Currently, any blueprint middleware registered, irrespective of which blueprint was used to do so, was
-being applied to all of the routes created by the :code:`@app` and :code:`@blueprint` alike.
-
-As part of this change, the blueprint based middleware application is enforced based on where they are
-registered.
-
-- If you register a middleware via :code:`@blueprint.middleware` then it will apply only to the routes defined by the blueprint.
-- If you register a middleware via :code:`@blueprint_group.middleware` then it will apply to all blueprint based routes that are part of the group.
-- If you define a middleware via :code:`@app.middleware` then it will be applied on all available routes