starred/sandman2-jeffknupp

Fork 0

mirror of https://github.com/jeffknupp/sandman2.git synced 2026-04-25 08:35:49 +03:00

[PR #127] [CLOSED] Scheduled weekly dependency update for week 40 #158

New issue

Closed

opened 2026-02-26 01:33:25 +03:00 by kerem · 0 comments

kerem commented

2026-02-26 01:33:25 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/jeffknupp/sandman2/pull/127
Author: @pyup-bot
Created: 10/7/2019
Status: ❌ Closed

Base: master ← Head: pyup-scheduled-update-2019-10-07

📝 Commits (5)

ae7845d Update sqlalchemy from 1.3.8 to 1.3.9
1c31f3e Update pytest from 5.2.0 to 5.2.1
f6e254c Update pytest-cov from 2.7.1 to 2.8.1
6f58749 Update werkzeug from 0.15.4 to 0.16.0
cff5364 Update zipp from 0.5.1 to 0.6.0

📊 Changes

1 file changed (+5 additions, -5 deletions)

View changed files

📝 requirements.txt (+5 -5)

📄 Description

Update SQLAlchemy from 1.3.8 to 1.3.9.

Changelog

1.3.9

:released: October 4, 2019

 .. change::
     :tags: usecase, engine
     :tickets: 4857

     Added new :func:`.create_engine` parameter
     :paramref:`.create_engine.max_identifier_length`. This overrides the
     dialect-coded &quot;max identifier length&quot; in order to accommodate for databases
     that have recently changed this length and the SQLAlchemy dialect has
     not yet been adjusted to detect for that version.  This parameter interacts
     with the existing :paramref:`.create_engine.label_length` parameter in that
     it establishes the maximum (and default) value for anonymously generated
     labels.   Additionally, post-connection detection of max identifier lengths
     has been added to the dialect system.  This feature is first being used
     by the Oracle dialect.

     .. seealso::

         :ref:`oracle_max_identifier_lengths` - in the Oracle dialect documentation

 .. change::
     :tags: usecase, oracle
     :tickets: 4857

     The Oracle dialect now emits a warning if Oracle version 12.2 or greater is
     used, and the :paramref:`.create_engine.max_identifier_length` parameter is
     not set.   The version in this specific case defaults to that of the
     &quot;compatibility&quot; version set in the Oracle server configuration, not the
     actual server version.   In version 1.4, the default max_identifier_length
     for 12.2 or greater will move to 128 characters.  In order to maintain
     forwards compatibility, applications should set
     :paramref:`.create_engine.max_identifier_length` to 30 in order to maintain
     the same length behavior, or to 128 in order to test the upcoming behavior.
     This length determines among other things how generated constraint names
     are truncated for statements like ``CREATE CONSTRAINT`` and ``DROP
     CONSTRAINT``, which means a the new length may produce a name-mismatch
     against a name that was generated with the old length, impacting database
     migrations.

     .. seealso::

         :ref:`oracle_max_identifier_lengths` - in the Oracle dialect documentation

 .. change::
     :tags: usecase, sqlite
     :tickets: 4863

     Added support for sqlite &quot;URI&quot; connections, which allow for sqlite-specific
     flags to be passed in the query string such as &quot;read only&quot; for Python
     sqlite3 drivers that support this.

     .. seealso::

         :ref:`pysqlite_uri_connections`

 .. change::
     :tags: bug, tests
     :tickets: 4285

     Fixed unit test regression released in 1.3.8 that would cause failure for
     Oracle, SQL Server and other non-native ENUM platforms due to new
     enumeration tests added as part of :ticket:`4285` enum sortability in the
     unit of work; the enumerations created constraints that were duplicated on
     name.

 .. change::
     :tags: bug, oracle
     :tickets: 4886

     Restored adding cx_Oracle.DATETIME to the setinputsizes() call when a
     SQLAlchemy :class:`.Date`, :class:`.DateTime` or :class:`.Time` datatype is
     used, as some complex queries require this to be present.  This was removed
     in the 1.2 series for arbitrary reasons.

 .. change::
     :tags: bug, mssql
     :tickets: 4883

     Added identifier quoting to the schema name applied to the &quot;use&quot; statement
     which is invoked when a SQL Server multipart schema name is used within  a
     :class:`.Table` that is being reflected, as well as for :class:`.Inspector`
     methods such as :meth:`.Inspector.get_table_names`; this accommodates for
     special characters or spaces in the database name.  Additionally, the &quot;use&quot;
     statement is not emitted if the current database matches the target owner
     database name being passed.

 .. change::
     :tags: bug, orm
     :tickets: 4872

     Fixed regression in selectinload loader strategy caused by :ticket:`4775`
     (released in version 1.3.6) where a many-to-one attribute of None would no
     longer be populated by the loader.  While this was usually not noticeable
     due to the lazyloader populating None upon get, it would lead to a detached
     instance error if the object were detached.

 .. change::
     :tags: bug, orm
     :tickets: 4873

     Passing a plain string expression to :meth:`.Session.query` is deprecated,
     as all string coercions were removed in :ticket:`4481` and this one should
     have been included.   The :func:`.literal_column` function may be used to
     produce a textual column expression.

 .. change::
     :tags: usecase, sql
     :tickets: 4847

     Added an explicit error message for the case when objects passed to
     :class:`.Table` are not :class:`.SchemaItem` objects, rather than resolving
     to an attribute error.


 .. change::
     :tags: bug, orm
     :tickets: 4890

     A warning is emitted for a condition in which the :class:`.Session` may
     implicitly swap an object out of the identity map for another one with the
     same primary key, detaching the old one, which can be an observed result of
     load operations which occur within the :meth:`.SessionEvents.after_flush`
     hook.  The warning is intended to notify the user that some special
     condition has caused this to happen and that the previous object may not be
     in the expected state.

 .. change::
     :tags: bug, sql
     :tickets: 4837

     Characters that interfere with &quot;pyformat&quot; or &quot;named&quot; formats in bound
     parameters, namely ``%, (, )`` and the space character, as well as a few
     other typically undesirable characters, are stripped early for a
     :func:`.bindparam` that is using an anonymized name, which is typically
     generated automatically from a named column which itself includes these
     characters in its name and does not use a ``.key``, so that they do not
     interfere either with the SQLAlchemy compiler&#39;s use of string formatting or
     with the driver-level parsing of the parameter, both of which could be
     demonstrated before the fix.  The change only applies to anonymized
     parameter names that are generated and consumed internally, not end-user
     defined names, so the change should have no impact on any existing code.
     Applies in particular to the psycopg2 driver which does not otherwise quote
     special parameter names, but also strips leading underscores to suit Oracle
     (but not yet leading numbers, as some anon parameters are currently
     entirely numeric/underscore based); Oracle in any case continues to quote
     parameter names that include special characters.

.. changelog::

Links

PyPI: https://pypi.org/project/sqlalchemy
Changelog: https://pyup.io/changelogs/sqlalchemy/
Homepage: http://www.sqlalchemy.org

Update pytest from 5.2.0 to 5.2.1.

Changelog

5.2.1

=========================

Bug Fixes
---------

- `5902 &lt;https://github.com/pytest-dev/pytest/issues/5902&gt;`_: Fix warnings about deprecated ``cmp`` attribute in ``attrs&gt;=19.2``.

Links

PyPI: https://pypi.org/project/pytest
Changelog: https://pyup.io/changelogs/pytest/
Homepage: https://docs.pytest.org/en/latest/

Update pytest-cov from 2.7.1 to 2.8.1.

Changelog

2.8.1

------------------

* Fixed `348 &lt;https://github.com/pytest-dev/pytest-cov/issues/348&gt;`_ -
regression when only certain reports (html or xml) are used then ``--cov-fail-under`` always fails.

2.8.0

------------------

* Fixed ``RecursionError`` that can occur when using
`cleanup_on_signal &lt;https://pytest-cov.readthedocs.io/en/latest/subprocess-support.htmlif-you-got-custom-signal-handling&gt;`__ or
`cleanup_on_sigterm &lt;https://pytest-cov.readthedocs.io/en/latest/subprocess-support.htmlif-you-got-custom-signal-handling&gt;`__.
See: `294 &lt;https://github.com/pytest-dev/pytest-cov/issues/294&gt;`_.
The 2.7.x releases of pytest-cov should be considered broken regarding aforementioned cleanup API.
* Added compatibility with future xdist release that deprecates some internals
(match pytest-xdist master/worker terminology).
Contributed by Thomas Grainger in `321 &lt;https://github.com/pytest-dev/pytest-cov/pull/321&gt;`_
* Fixed breakage that occurs when multiple reporting options are used.
Contributed by Thomas Grainger in `338 &lt;https://github.com/pytest-dev/pytest-cov/pull/338&gt;`_.
* Changed internals to use a stub instead of ``os.devnull``.
Contributed by Thomas Grainger in `332 &lt;https://github.com/pytest-dev/pytest-cov/pull/332&gt;`_.
* Added support for Coverage 5.0.
Contributed by Ned Batchelder in `319 &lt;https://github.com/pytest-dev/pytest-cov/pull/319&gt;`_.
* Added support for float values in ``--cov-fail-under``.
Contributed by Martín Gaitán in `311 &lt;https://github.com/pytest-dev/pytest-cov/pull/311&gt;`_.
* Various documentation fixes. Contributed by
Juanjo Bazán,
Andrew Murray and
Albert Tugushev in
`298 &lt;https://github.com/pytest-dev/pytest-cov/pull/298&gt;`_,
`299 &lt;https://github.com/pytest-dev/pytest-cov/pull/299&gt;`_ and
`307 &lt;https://github.com/pytest-dev/pytest-cov/pull/307&gt;`_.
* Various testing improvements. Contributed by
Ned Batchelder,
Daniel Hahler,
Ionel Cristian Mărieș and
Hugo van Kemenade in
`313 &lt;https://github.com/pytest-dev/pytest-cov/pull/313&gt;`_,
`314 &lt;https://github.com/pytest-dev/pytest-cov/pull/314&gt;`_,
`315 &lt;https://github.com/pytest-dev/pytest-cov/pull/315&gt;`_,
`316 &lt;https://github.com/pytest-dev/pytest-cov/pull/316&gt;`_,
`325 &lt;https://github.com/pytest-dev/pytest-cov/pull/325&gt;`_,
`326 &lt;https://github.com/pytest-dev/pytest-cov/pull/326&gt;`_,
`334 &lt;https://github.com/pytest-dev/pytest-cov/pull/334&gt;`_ and
`335 &lt;https://github.com/pytest-dev/pytest-cov/pull/335&gt;`_.
* Added the ``--cov-context`` CLI options that enables coverage contexts. Only works with coverage 5.0+.
Contributed by Ned Batchelder in `345 &lt;https://github.com/pytest-dev/pytest-cov/pull/345&gt;`_.

Links

PyPI: https://pypi.org/project/pytest-cov
Changelog: https://pyup.io/changelogs/pytest-cov/
Repo: https://github.com/pytest-dev/pytest-cov

Update Werkzeug from 0.15.4 to 0.16.0.

Changelog

0.16.0

--------------

Unreleased

-   Deprecate most top-level attributes provided by the ``werkzeug``
 module in favor of direct imports. The deprecated imports will be
 removed in version 1.0.

 For example, instead of ``import werkzeug; werkzeug.url_quote``, do
 ``from werkzeug.urls import url_quote``. A deprecation warning will
 show the correct import to use. ``werkzeug.exceptions`` and
 ``werkzeug.routing`` should also be imported instead of accessed,
 but for technical reasons can&#39;t show a warning.

 :issue:`2`, :pr:`1640`

0.15.6

--------------

Released 2019-09-04

-   Work around a bug in pip that caused the reloader to fail on
 Windows when the script was an entry point. This fixes the issue
 with Flask&#39;s `flask run` command failing with &quot;No module named
 Scripts\flask&quot;. :issue:`1614`
-   ``ProxyFix`` trusts the ``X-Forwarded-Proto`` header by default.
 :issue:`1630`
-   The deprecated ``num_proxies`` argument to ``ProxyFix`` sets
 ``x_for``, ``x_proto``, and ``x_host`` to match 0.14 behavior. This
 is intended to make intermediate upgrades less disruptive, but the
 argument will still be removed in 1.0. :issue:`1630`

0.15.5

--------------

Released 2019-07-17

-   Fix a ``TypeError`` due to changes to ``ast.Module`` in Python 3.8.
 :issue:`1551`
-   Fix a C assertion failure in debug builds of some Python 2.7
 releases. :issue:`1553`
-   :class:`~exceptions.BadRequestKeyError` adds the ``KeyError``
 message to the description if ``e.show_exception`` is set to
 ``True``. This is a more secure default than the original 0.15.0
 behavior and makes it easier to control without losing information.
 :pr:`1592`
-   Upgrade the debugger to jQuery 3.4.1. :issue:`1581`
-   Work around an issue in some external debuggers that caused the
 reloader to fail. :issue:`1607`
-   Work around an issue where the reloader couldn&#39;t introspect a
 setuptools script installed as an egg. :issue:`1600`
-   The reloader will use ``sys.executable`` even if the script is
 marked executable, reverting a behavior intended for NixOS
 introduced in 0.15. The reloader should no longer cause
 ``OSError: [Errno 8] Exec format error``. :issue:`1482`,
 :issue:`1580`
-   ``SharedDataMiddleware`` safely handles paths with Windows drive
 names. :issue:`1589`

Links

PyPI: https://pypi.org/project/werkzeug
Changelog: https://pyup.io/changelogs/werkzeug/
Homepage: https://palletsprojects.com/p/werkzeug/

Update zipp from 0.5.1 to 0.6.0.

Changelog

0.6.0

======

12: When adding implicit dirs, ensure that ancestral directories
are added and that duplicates are excluded.

The library now relies on
`more_itertools &lt;https://pypi.org/project/more_itertools&gt;`_.

0.5.2

======

7: Parent of a directory now actually returns the parent.

Links

PyPI: https://pypi.org/project/zipp
Changelog: https://pyup.io/changelogs/zipp/
Repo: https://github.com/jaraco/zipp

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/jeffknupp/sandman2/pull/127 **Author:** [@pyup-bot](https://github.com/pyup-bot) **Created:** 10/7/2019 **Status:** ❌ Closed **Base:** `master` ← **Head:** `pyup-scheduled-update-2019-10-07` --- ### 📝 Commits (5) - [`ae7845d`](https://github.com/jeffknupp/sandman2/commit/ae7845d899cbfe96c34706cc5e39ca68f8ee3771) Update sqlalchemy from 1.3.8 to 1.3.9 - [`1c31f3e`](https://github.com/jeffknupp/sandman2/commit/1c31f3e4302689f769eece78cc3e0fe978ec94a6) Update pytest from 5.2.0 to 5.2.1 - [`f6e254c`](https://github.com/jeffknupp/sandman2/commit/f6e254c7ccc38fa1ebffb839c621c18c4182f2f8) Update pytest-cov from 2.7.1 to 2.8.1 - [`6f58749`](https://github.com/jeffknupp/sandman2/commit/6f58749b08e05488e337f6e86fd18a2ed46010f8) Update werkzeug from 0.15.4 to 0.16.0 - [`cff5364`](https://github.com/jeffknupp/sandman2/commit/cff53647fb6c4fd8a9cfff4474d1844a0e7fb25f) Update zipp from 0.5.1 to 0.6.0 ### 📊 Changes **1 file changed** (+5 additions, -5 deletions) <details> <summary>View changed files</summary> 📝 `requirements.txt` (+5 -5) </details> ### 📄 Description ### Update [SQLAlchemy](https://pypi.org/project/SQLAlchemy) from **1.3.8** to **1.3.9**. <details> <summary>Changelog</summary> ### 1.3.9 ``` :released: October 4, 2019 .. change:: :tags: usecase, engine :tickets: 4857 Added new :func:`.create_engine` parameter :paramref:`.create_engine.max_identifier_length`. This overrides the dialect-coded "max identifier length" in order to accommodate for databases that have recently changed this length and the SQLAlchemy dialect has not yet been adjusted to detect for that version. This parameter interacts with the existing :paramref:`.create_engine.label_length` parameter in that it establishes the maximum (and default) value for anonymously generated labels. Additionally, post-connection detection of max identifier lengths has been added to the dialect system. This feature is first being used by the Oracle dialect. .. seealso:: :ref:`oracle_max_identifier_lengths` - in the Oracle dialect documentation .. change:: :tags: usecase, oracle :tickets: 4857 The Oracle dialect now emits a warning if Oracle version 12.2 or greater is used, and the :paramref:`.create_engine.max_identifier_length` parameter is not set. The version in this specific case defaults to that of the "compatibility" version set in the Oracle server configuration, not the actual server version. In version 1.4, the default max_identifier_length for 12.2 or greater will move to 128 characters. In order to maintain forwards compatibility, applications should set :paramref:`.create_engine.max_identifier_length` to 30 in order to maintain the same length behavior, or to 128 in order to test the upcoming behavior. This length determines among other things how generated constraint names are truncated for statements like ``CREATE CONSTRAINT`` and ``DROP CONSTRAINT``, which means a the new length may produce a name-mismatch against a name that was generated with the old length, impacting database migrations. .. seealso:: :ref:`oracle_max_identifier_lengths` - in the Oracle dialect documentation .. change:: :tags: usecase, sqlite :tickets: 4863 Added support for sqlite "URI" connections, which allow for sqlite-specific flags to be passed in the query string such as "read only" for Python sqlite3 drivers that support this. .. seealso:: :ref:`pysqlite_uri_connections` .. change:: :tags: bug, tests :tickets: 4285 Fixed unit test regression released in 1.3.8 that would cause failure for Oracle, SQL Server and other non-native ENUM platforms due to new enumeration tests added as part of :ticket:`4285` enum sortability in the unit of work; the enumerations created constraints that were duplicated on name. .. change:: :tags: bug, oracle :tickets: 4886 Restored adding cx_Oracle.DATETIME to the setinputsizes() call when a SQLAlchemy :class:`.Date`, :class:`.DateTime` or :class:`.Time` datatype is used, as some complex queries require this to be present. This was removed in the 1.2 series for arbitrary reasons. .. change:: :tags: bug, mssql :tickets: 4883 Added identifier quoting to the schema name applied to the "use" statement which is invoked when a SQL Server multipart schema name is used within a :class:`.Table` that is being reflected, as well as for :class:`.Inspector` methods such as :meth:`.Inspector.get_table_names`; this accommodates for special characters or spaces in the database name. Additionally, the "use" statement is not emitted if the current database matches the target owner database name being passed. .. change:: :tags: bug, orm :tickets: 4872 Fixed regression in selectinload loader strategy caused by :ticket:`4775` (released in version 1.3.6) where a many-to-one attribute of None would no longer be populated by the loader. While this was usually not noticeable due to the lazyloader populating None upon get, it would lead to a detached instance error if the object were detached. .. change:: :tags: bug, orm :tickets: 4873 Passing a plain string expression to :meth:`.Session.query` is deprecated, as all string coercions were removed in :ticket:`4481` and this one should have been included. The :func:`.literal_column` function may be used to produce a textual column expression. .. change:: :tags: usecase, sql :tickets: 4847 Added an explicit error message for the case when objects passed to :class:`.Table` are not :class:`.SchemaItem` objects, rather than resolving to an attribute error. .. change:: :tags: bug, orm :tickets: 4890 A warning is emitted for a condition in which the :class:`.Session` may implicitly swap an object out of the identity map for another one with the same primary key, detaching the old one, which can be an observed result of load operations which occur within the :meth:`.SessionEvents.after_flush` hook. The warning is intended to notify the user that some special condition has caused this to happen and that the previous object may not be in the expected state. .. change:: :tags: bug, sql :tickets: 4837 Characters that interfere with "pyformat" or "named" formats in bound parameters, namely ``%, (, )`` and the space character, as well as a few other typically undesirable characters, are stripped early for a :func:`.bindparam` that is using an anonymized name, which is typically generated automatically from a named column which itself includes these characters in its name and does not use a ``.key``, so that they do not interfere either with the SQLAlchemy compiler's use of string formatting or with the driver-level parsing of the parameter, both of which could be demonstrated before the fix. The change only applies to anonymized parameter names that are generated and consumed internally, not end-user defined names, so the change should have no impact on any existing code. Applies in particular to the psycopg2 driver which does not otherwise quote special parameter names, but also strips leading underscores to suit Oracle (but not yet leading numbers, as some anon parameters are currently entirely numeric/underscore based); Oracle in any case continues to quote parameter names that include special characters. .. changelog:: ``` </details> <details> <summary>Links</summary> - PyPI: https://pypi.org/project/sqlalchemy - Changelog: https://pyup.io/changelogs/sqlalchemy/ - Homepage: http://www.sqlalchemy.org </details> ### Update [pytest](https://pypi.org/project/pytest) from **5.2.0** to **5.2.1**. <details> <summary>Changelog</summary> ### 5.2.1 ``` ========================= Bug Fixes --------- - `5902 <https://github.com/pytest-dev/pytest/issues/5902>`_: Fix warnings about deprecated ``cmp`` attribute in ``attrs>=19.2``. ``` </details> <details> <summary>Links</summary> - PyPI: https://pypi.org/project/pytest - Changelog: https://pyup.io/changelogs/pytest/ - Homepage: https://docs.pytest.org/en/latest/ </details> ### Update [pytest-cov](https://pypi.org/project/pytest-cov) from **2.7.1** to **2.8.1**. <details> <summary>Changelog</summary> ### 2.8.1 ``` ------------------ * Fixed `348 <https://github.com/pytest-dev/pytest-cov/issues/348>`_ - regression when only certain reports (html or xml) are used then ``--cov-fail-under`` always fails. ``` ### 2.8.0 ``` ------------------ * Fixed ``RecursionError`` that can occur when using `cleanup_on_signal <https://pytest-cov.readthedocs.io/en/latest/subprocess-support.htmlif-you-got-custom-signal-handling>`__ or `cleanup_on_sigterm <https://pytest-cov.readthedocs.io/en/latest/subprocess-support.htmlif-you-got-custom-signal-handling>`__. See: `294 <https://github.com/pytest-dev/pytest-cov/issues/294>`_. The 2.7.x releases of pytest-cov should be considered broken regarding aforementioned cleanup API. * Added compatibility with future xdist release that deprecates some internals (match pytest-xdist master/worker terminology). Contributed by Thomas Grainger in `321 <https://github.com/pytest-dev/pytest-cov/pull/321>`_ * Fixed breakage that occurs when multiple reporting options are used. Contributed by Thomas Grainger in `338 <https://github.com/pytest-dev/pytest-cov/pull/338>`_. * Changed internals to use a stub instead of ``os.devnull``. Contributed by Thomas Grainger in `332 <https://github.com/pytest-dev/pytest-cov/pull/332>`_. * Added support for Coverage 5.0. Contributed by Ned Batchelder in `319 <https://github.com/pytest-dev/pytest-cov/pull/319>`_. * Added support for float values in ``--cov-fail-under``. Contributed by Martín Gaitán in `311 <https://github.com/pytest-dev/pytest-cov/pull/311>`_. * Various documentation fixes. Contributed by Juanjo Bazán, Andrew Murray and Albert Tugushev in `298 <https://github.com/pytest-dev/pytest-cov/pull/298>`_, `299 <https://github.com/pytest-dev/pytest-cov/pull/299>`_ and `307 <https://github.com/pytest-dev/pytest-cov/pull/307>`_. * Various testing improvements. Contributed by Ned Batchelder, Daniel Hahler, Ionel Cristian Mărieș and Hugo van Kemenade in `313 <https://github.com/pytest-dev/pytest-cov/pull/313>`_, `314 <https://github.com/pytest-dev/pytest-cov/pull/314>`_, `315 <https://github.com/pytest-dev/pytest-cov/pull/315>`_, `316 <https://github.com/pytest-dev/pytest-cov/pull/316>`_, `325 <https://github.com/pytest-dev/pytest-cov/pull/325>`_, `326 <https://github.com/pytest-dev/pytest-cov/pull/326>`_, `334 <https://github.com/pytest-dev/pytest-cov/pull/334>`_ and `335 <https://github.com/pytest-dev/pytest-cov/pull/335>`_. * Added the ``--cov-context`` CLI options that enables coverage contexts. Only works with coverage 5.0+. Contributed by Ned Batchelder in `345 <https://github.com/pytest-dev/pytest-cov/pull/345>`_. ``` </details> <details> <summary>Links</summary> - PyPI: https://pypi.org/project/pytest-cov - Changelog: https://pyup.io/changelogs/pytest-cov/ - Repo: https://github.com/pytest-dev/pytest-cov </details> ### Update [Werkzeug](https://pypi.org/project/Werkzeug) from **0.15.4** to **0.16.0**. <details> <summary>Changelog</summary> ### 0.16.0 ``` -------------- Unreleased - Deprecate most top-level attributes provided by the ``werkzeug`` module in favor of direct imports. The deprecated imports will be removed in version 1.0. For example, instead of ``import werkzeug; werkzeug.url_quote``, do ``from werkzeug.urls import url_quote``. A deprecation warning will show the correct import to use. ``werkzeug.exceptions`` and ``werkzeug.routing`` should also be imported instead of accessed, but for technical reasons can't show a warning. :issue:`2`, :pr:`1640` ``` ### 0.15.6 ``` -------------- Released 2019-09-04 - Work around a bug in pip that caused the reloader to fail on Windows when the script was an entry point. This fixes the issue with Flask's `flask run` command failing with "No module named Scripts\flask". :issue:`1614` - ``ProxyFix`` trusts the ``X-Forwarded-Proto`` header by default. :issue:`1630` - The deprecated ``num_proxies`` argument to ``ProxyFix`` sets ``x_for``, ``x_proto``, and ``x_host`` to match 0.14 behavior. This is intended to make intermediate upgrades less disruptive, but the argument will still be removed in 1.0. :issue:`1630` ``` ### 0.15.5 ``` -------------- Released 2019-07-17 - Fix a ``TypeError`` due to changes to ``ast.Module`` in Python 3.8. :issue:`1551` - Fix a C assertion failure in debug builds of some Python 2.7 releases. :issue:`1553` - :class:`~exceptions.BadRequestKeyError` adds the ``KeyError`` message to the description if ``e.show_exception`` is set to ``True``. This is a more secure default than the original 0.15.0 behavior and makes it easier to control without losing information. :pr:`1592` - Upgrade the debugger to jQuery 3.4.1. :issue:`1581` - Work around an issue in some external debuggers that caused the reloader to fail. :issue:`1607` - Work around an issue where the reloader couldn't introspect a setuptools script installed as an egg. :issue:`1600` - The reloader will use ``sys.executable`` even if the script is marked executable, reverting a behavior intended for NixOS introduced in 0.15. The reloader should no longer cause ``OSError: [Errno 8] Exec format error``. :issue:`1482`, :issue:`1580` - ``SharedDataMiddleware`` safely handles paths with Windows drive names. :issue:`1589` ``` </details> <details> <summary>Links</summary> - PyPI: https://pypi.org/project/werkzeug - Changelog: https://pyup.io/changelogs/werkzeug/ - Homepage: https://palletsprojects.com/p/werkzeug/ </details> ### Update [zipp](https://pypi.org/project/zipp) from **0.5.1** to **0.6.0**. <details> <summary>Changelog</summary> ### 0.6.0 ``` ====== 12: When adding implicit dirs, ensure that ancestral directories are added and that duplicates are excluded. The library now relies on `more_itertools <https://pypi.org/project/more_itertools>`_. ``` ### 0.5.2 ``` ====== 7: Parent of a directory now actually returns the parent. ``` </details> <details> <summary>Links</summary> - PyPI: https://pypi.org/project/zipp - Changelog: https://pyup.io/changelogs/zipp/ - Repo: https://github.com/jaraco/zipp </details> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>