[PR #196] [CLOSED] Scheduled weekly dependency update for week 03 #219

New issue

Closed

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

kerem commented

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

Owner

📋 Pull Request Information

Original PR: https://github.com/jeffknupp/sandman2/pull/196
Author: @pyup-bot
Created: 1/18/2021
Status: ❌ Closed

Base: master ← Head: pyup-scheduled-update-2021-01-18

📝 Commits (5)

cb72ce5 Update sqlalchemy from 1.3.20 to 1.3.22
aff1725 Update coverage from 5.3 to 5.3.1
b42d3f4 Update pytest from 6.2.0 to 6.2.1
9916bc7 Update flask-cors from 3.0.9 to 3.0.10
cbbab87 Update pytest-cov from 2.10.1 to 2.11.0

📊 Changes

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

View changed files

📝 requirements.txt (+5 -5)

📄 Description

Update SQLAlchemy from 1.3.20 to 1.3.22.

Changelog

1.3.22

:released: December 18, 2020

 .. change::
     :tags: bug, oracle
     :tickets: 5784
     :versions: 1.4.0b2

     Fixed regression which occured due to :ticket:`5755` which implemented
     isolation level support for Oracle.   It has been reported that many Oracle
     accounts don&#39;t actually have permission to query the ``v$transaction``
     view so this feature has been altered to gracefully fallback when it fails
     upon database connect, where the dialect will assume &quot;READ COMMITTED&quot; is
     the default isolation level as was the case prior to SQLAlchemy 1.3.21.
     However, explicit use of the :meth:`_engine.Connection.get_isolation_level`
     method must now necessarily raise an exception, as Oracle databases with
     this restriction explicitly disallow the user from reading the current
     isolation level.

.. changelog::

1.3.21

:released: December 17, 2020

 .. change::
     :tags: bug, orm
     :tickets: 5774
     :versions: 1.4.0b2

     Added a comprehensive check and an informative error message for the case
     where a mapped class, or a string mapped class name, is passed to
     :paramref:`_orm.relationship.secondary`.  This is an extremely common error
     which warrants a clear message.

     Additionally, added a new rule to the class registry resolution such that
     with regards to the :paramref:`_orm.relationship.secondary` parameter, if a
     mapped class and its table are of the identical string name, the
     :class:`.Table` will be favored when resolving this parameter.   In all
     other cases, the class continues to be favored if a class and table
     share the identical name.

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

     Added ``sqlite_with_rowid=False`` dialect keyword to enable creating
     tables as ``CREATE TABLE … WITHOUT ROWID``. Patch courtesy Sean Anderson.

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

     A warning is emmitted if a returning() method such as
     :meth:`_sql.Insert.returning` is called multiple times, as this does not
     yet support additive operation.  Version 1.4 will support additive
     operation for this.  Additionally, any combination of the
     :meth:`_sql.Insert.returning` and :meth:`_sql.ValuesBase.return_defaults`
     methods now raises an error as these methods are mutually exclusive;
     previously the operation would fail silently.


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

     Fixed bug where a CREATE INDEX statement was rendered incorrectly when
     both ``mssql-include`` and ``mssql_where`` were specified. Pull request
     courtesy Adiorz.

 .. change::
     :tags: bug, postgresql, mysql
     :tickets: 5729
     :versions: 1.4.0b2

     Fixed regression introduced in 1.3.2 for the PostgreSQL dialect, also
     copied out to the MySQL dialect&#39;s feature in 1.3.18, where usage of a non
     :class:`_schema.Table` construct such as :func:`_sql.text` as the argument
     to :paramref:`_sql.Select.with_for_update.of` would fail to be accommodated
     correctly within the PostgreSQL or MySQL compilers.


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

     Added SQL Server code &quot;01000&quot; to the list of disconnect codes.


 .. change::
     :tags: usecase, postgresql
     :tickets: 5604
     :versions: 1.4.0b2

     Added new parameter :paramref:`_postgresql.ExcludeConstraint.ops` to the
     :class:`_postgresql.ExcludeConstraint` object, to support operator class
     specification with this constraint.  Pull request courtesy Alon Menczer.

 .. change::
     :tags: bug, mysql, reflection
     :tickets: 5744
     :versions: 1.4.0b2

     Fixed issue where reflecting a server default on MariaDB only that
     contained a decimal point in the value would fail to be reflected
     correctly, leading towards a reflected table that lacked any server
     default.


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

     Fixed bug in :meth:`_query.Query.update` where objects in the
     :class:`_ormsession.Session` that were already expired would be
     unnecessarily SELECTed individually when they were refreshed by the
     &quot;evaluate&quot;synchronize strategy.

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

     Implemented support for the SERIALIZABLE isolation level for Oracle
     databases, as well as a real implementation for
     :meth:`_engine.Connection.get_isolation_level`.

     .. seealso::

         :ref:`oracle_isolation_level`

 .. change::
     :tags: mysql, sql
     :tickets: 5696

     Added missing keywords to the ``RESERVED_WORDS`` list for the MySQL
     dialect: ``action``, ``level``, ``mode``, ``status``, ``text``, ``time``.
     Pull request courtesy Oscar Batori.

 .. change::
     :tags: bug, orm
     :tickets: 5737
     :versions: 1.4.0b2

     Fixed bug involving the ``restore_load_context`` option of ORM events such
     as :meth:`_ormevent.InstanceEvents.load` such that the flag would not be
     carried along to subclasses which were mapped after the event handler were
     first established.



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

     Fixed structural compiler issue where some constructs such as MySQL /
     PostgreSQL &quot;on conflict / on duplicate key&quot; would rely upon the state of
     the :class:`_sql.Compiler` object being fixed against their statement as
     the top level statement, which would fail in cases where those statements
     are branched from a different context, such as a DDL construct linked to a
     SQL statement.


 .. change::
     :tags: mssql, sqlite, reflection
     :tickets: 5661

     Fixed issue with composite primary key columns not being reported
     in the correct order. Patch courtesy fulpm.

.. changelog::

Links

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

Update coverage from 5.3 to 5.3.1.

Changelog

5.3.1

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

- When using ``--source`` on a large source tree, v5.x was slower than previous
versions.  This performance regression is now fixed, closing `issue 1037`_.

- Mysterious SQLite errors can happen on PyPy, as reported in `issue 1010`_. An
immediate retry seems to fix the problem, although it is an unsatisfying
solution.

- The HTML report now saves the sort order in a more widely supported way,
fixing `issue 986`_.  Thanks, Sebastián Ramírez (`pull request 1066`_).

- The HTML report pages now have a :ref:`Sleepy Snake &lt;sleepy&gt;` favicon.

- Wheels are now provided for manylinux2010, and for PyPy3 (pp36 and pp37).

- Continuous integration has moved from Travis and AppVeyor to GitHub Actions.

.. _issue 986: https://github.com/nedbat/coveragepy/issues/986
.. _issue 1037: https://github.com/nedbat/coveragepy/issues/1037
.. _issue 1010: https://github.com/nedbat/coveragepy/issues/1010
.. _pull request 1066: https://github.com/nedbat/coveragepy/pull/1066

.. _changes_53:

Links

PyPI: https://pypi.org/project/coverage
Changelog: https://pyup.io/changelogs/coverage/
Repo: https://github.com/nedbat/coveragepy

Update pytest from 6.2.0 to 6.2.1.

The bot wasn't able to find a changelog for this release. Got an idea?

Links

PyPI: https://pypi.org/project/pytest
Homepage: https://docs.pytest.org/en/latest/

Update Flask-Cors from 3.0.9 to 3.0.10.

Changelog

3.0.10

Adds support for PPC64 and ARM64 builds for distribution. Thanks sreekanth370

Links

PyPI: https://pypi.org/project/flask-cors
Changelog: https://pyup.io/changelogs/flask-cors/
Repo: https://github.com/corydolphin/flask-cors

Update pytest-cov from 2.10.1 to 2.11.0.

Changelog

2.11.0

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

* Bumped minimum coverage requirement to 5.2.1. This prevents reporting issues.
Contributed by Mateus Berardo de Souza Terra in `433 &lt;https://github.com/pytest-dev/pytest-cov/pull/433&gt;`_.
* Improved sample projects (from the `examples &lt;https://github.com/pytest-dev/pytest-cov/tree/master/examples&gt;`_
directory) to support running `tox -e pyXY`. Now the example configures a suffixed coverage data file,
and that makes the cleanup environment unnecessary.
Contributed by Ganden Schaffner in `435 &lt;https://github.com/pytest-dev/pytest-cov/pull/435&gt;`_.
* Removed the empty `console_scripts` entrypoint that confused some Gentoo build script.
I didn&#39;t ask why it was so broken cause I didn&#39;t want to ruin my day.
Contributed by Michał Górny in `434 &lt;https://github.com/pytest-dev/pytest-cov/pull/434&gt;`_.
* Fixed the missing `coverage context &lt;https://coverage.readthedocs.io/en/stable/contexts.html&gt;`_
when using subprocesses.
Contributed by Bernát Gábor in `443 &lt;https://github.com/pytest-dev/pytest-cov/pull/443&gt;`_.
* Updated the config section in the docs.
Contributed by Pamela McA&#39;Nulty in `429 &lt;https://github.com/pytest-dev/pytest-cov/pull/429&gt;`_.
* Migrated CI to travis-ci.com (from .org).

Links

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

_{🔄 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/196 **Author:** [@pyup-bot](https://github.com/pyup-bot) **Created:** 1/18/2021 **Status:** ❌ Closed **Base:** `master` ← **Head:** `pyup-scheduled-update-2021-01-18` --- ### 📝 Commits (5) - [`cb72ce5`](https://github.com/jeffknupp/sandman2/commit/cb72ce5ac77ca9d3dd9732c3957d779c46a6291e) Update sqlalchemy from 1.3.20 to 1.3.22 - [`aff1725`](https://github.com/jeffknupp/sandman2/commit/aff1725bd4df7684118835c508199e192d1014ad) Update coverage from 5.3 to 5.3.1 - [`b42d3f4`](https://github.com/jeffknupp/sandman2/commit/b42d3f42b2b961dc94bd070a1fc94d381b11ff15) Update pytest from 6.2.0 to 6.2.1 - [`9916bc7`](https://github.com/jeffknupp/sandman2/commit/9916bc7b74405f13d8d58332f2d2dcb9cf8e2aab) Update flask-cors from 3.0.9 to 3.0.10 - [`cbbab87`](https://github.com/jeffknupp/sandman2/commit/cbbab8775f4e9a89c4c6b1a2d0786318257709cb) Update pytest-cov from 2.10.1 to 2.11.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.20** to **1.3.22**. <details> <summary>Changelog</summary> ### 1.3.22 ``` :released: December 18, 2020 .. change:: :tags: bug, oracle :tickets: 5784 :versions: 1.4.0b2 Fixed regression which occured due to :ticket:`5755` which implemented isolation level support for Oracle. It has been reported that many Oracle accounts don't actually have permission to query the ``v$transaction`` view so this feature has been altered to gracefully fallback when it fails upon database connect, where the dialect will assume "READ COMMITTED" is the default isolation level as was the case prior to SQLAlchemy 1.3.21. However, explicit use of the :meth:`_engine.Connection.get_isolation_level` method must now necessarily raise an exception, as Oracle databases with this restriction explicitly disallow the user from reading the current isolation level. .. changelog:: ``` ### 1.3.21 ``` :released: December 17, 2020 .. change:: :tags: bug, orm :tickets: 5774 :versions: 1.4.0b2 Added a comprehensive check and an informative error message for the case where a mapped class, or a string mapped class name, is passed to :paramref:`_orm.relationship.secondary`. This is an extremely common error which warrants a clear message. Additionally, added a new rule to the class registry resolution such that with regards to the :paramref:`_orm.relationship.secondary` parameter, if a mapped class and its table are of the identical string name, the :class:`.Table` will be favored when resolving this parameter. In all other cases, the class continues to be favored if a class and table share the identical name. .. change:: :tags: sqlite, usecase :tickets: 5685 Added ``sqlite_with_rowid=False`` dialect keyword to enable creating tables as ``CREATE TABLE … WITHOUT ROWID``. Patch courtesy Sean Anderson. .. change:: :tags: bug, sql :tickets: 5691 A warning is emmitted if a returning() method such as :meth:`_sql.Insert.returning` is called multiple times, as this does not yet support additive operation. Version 1.4 will support additive operation for this. Additionally, any combination of the :meth:`_sql.Insert.returning` and :meth:`_sql.ValuesBase.return_defaults` methods now raises an error as these methods are mutually exclusive; previously the operation would fail silently. .. change:: :tags: bug, mssql :tickets: 5751 Fixed bug where a CREATE INDEX statement was rendered incorrectly when both ``mssql-include`` and ``mssql_where`` were specified. Pull request courtesy Adiorz. .. change:: :tags: bug, postgresql, mysql :tickets: 5729 :versions: 1.4.0b2 Fixed regression introduced in 1.3.2 for the PostgreSQL dialect, also copied out to the MySQL dialect's feature in 1.3.18, where usage of a non :class:`_schema.Table` construct such as :func:`_sql.text` as the argument to :paramref:`_sql.Select.with_for_update.of` would fail to be accommodated correctly within the PostgreSQL or MySQL compilers. .. change:: :tags: bug, mssql :tickets: 5646 Added SQL Server code "01000" to the list of disconnect codes. .. change:: :tags: usecase, postgresql :tickets: 5604 :versions: 1.4.0b2 Added new parameter :paramref:`_postgresql.ExcludeConstraint.ops` to the :class:`_postgresql.ExcludeConstraint` object, to support operator class specification with this constraint. Pull request courtesy Alon Menczer. .. change:: :tags: bug, mysql, reflection :tickets: 5744 :versions: 1.4.0b2 Fixed issue where reflecting a server default on MariaDB only that contained a decimal point in the value would fail to be reflected correctly, leading towards a reflected table that lacked any server default. .. change:: :tags: bug, orm :tickets: 5664 Fixed bug in :meth:`_query.Query.update` where objects in the :class:`_ormsession.Session` that were already expired would be unnecessarily SELECTed individually when they were refreshed by the "evaluate"synchronize strategy. .. change:: :tags: usecase, oracle :tickets: 5755 Implemented support for the SERIALIZABLE isolation level for Oracle databases, as well as a real implementation for :meth:`_engine.Connection.get_isolation_level`. .. seealso:: :ref:`oracle_isolation_level` .. change:: :tags: mysql, sql :tickets: 5696 Added missing keywords to the ``RESERVED_WORDS`` list for the MySQL dialect: ``action``, ``level``, ``mode``, ``status``, ``text``, ``time``. Pull request courtesy Oscar Batori. .. change:: :tags: bug, orm :tickets: 5737 :versions: 1.4.0b2 Fixed bug involving the ``restore_load_context`` option of ORM events such as :meth:`_ormevent.InstanceEvents.load` such that the flag would not be carried along to subclasses which were mapped after the event handler were first established. .. change:: :tags: bug, sql :tickets: 5656 Fixed structural compiler issue where some constructs such as MySQL / PostgreSQL "on conflict / on duplicate key" would rely upon the state of the :class:`_sql.Compiler` object being fixed against their statement as the top level statement, which would fail in cases where those statements are branched from a different context, such as a DDL construct linked to a SQL statement. .. change:: :tags: mssql, sqlite, reflection :tickets: 5661 Fixed issue with composite primary key columns not being reported in the correct order. Patch courtesy fulpm. .. 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 [coverage](https://pypi.org/project/coverage) from **5.3** to **5.3.1**. <details> <summary>Changelog</summary> ### 5.3.1 ``` ---------------------------- - When using ``--source`` on a large source tree, v5.x was slower than previous versions. This performance regression is now fixed, closing `issue 1037`_. - Mysterious SQLite errors can happen on PyPy, as reported in `issue 1010`_. An immediate retry seems to fix the problem, although it is an unsatisfying solution. - The HTML report now saves the sort order in a more widely supported way, fixing `issue 986`_. Thanks, Sebastián Ramírez (`pull request 1066`_). - The HTML report pages now have a :ref:`Sleepy Snake <sleepy>` favicon. - Wheels are now provided for manylinux2010, and for PyPy3 (pp36 and pp37). - Continuous integration has moved from Travis and AppVeyor to GitHub Actions. .. _issue 986: https://github.com/nedbat/coveragepy/issues/986 .. _issue 1037: https://github.com/nedbat/coveragepy/issues/1037 .. _issue 1010: https://github.com/nedbat/coveragepy/issues/1010 .. _pull request 1066: https://github.com/nedbat/coveragepy/pull/1066 .. _changes_53: ``` </details> <details> <summary>Links</summary> - PyPI: https://pypi.org/project/coverage - Changelog: https://pyup.io/changelogs/coverage/ - Repo: https://github.com/nedbat/coveragepy </details> ### Update [pytest](https://pypi.org/project/pytest) from **6.2.0** to **6.2.1**. *The bot wasn't able to find a changelog for this release. [Got an idea?](https://github.com/pyupio/changelogs/issues/new)* <details> <summary>Links</summary> - PyPI: https://pypi.org/project/pytest - Homepage: https://docs.pytest.org/en/latest/ </details> ### Update [Flask-Cors](https://pypi.org/project/Flask-Cors) from **3.0.9** to **3.0.10**. <details> <summary>Changelog</summary> ### 3.0.10 ``` Adds support for PPC64 and ARM64 builds for distribution. Thanks sreekanth370 ``` </details> <details> <summary>Links</summary> - PyPI: https://pypi.org/project/flask-cors - Changelog: https://pyup.io/changelogs/flask-cors/ - Repo: https://github.com/corydolphin/flask-cors </details> ### Update [pytest-cov](https://pypi.org/project/pytest-cov) from **2.10.1** to **2.11.0**. <details> <summary>Changelog</summary> ### 2.11.0 ``` ------------------- * Bumped minimum coverage requirement to 5.2.1. This prevents reporting issues. Contributed by Mateus Berardo de Souza Terra in `433 <https://github.com/pytest-dev/pytest-cov/pull/433>`_. * Improved sample projects (from the `examples <https://github.com/pytest-dev/pytest-cov/tree/master/examples>`_ directory) to support running `tox -e pyXY`. Now the example configures a suffixed coverage data file, and that makes the cleanup environment unnecessary. Contributed by Ganden Schaffner in `435 <https://github.com/pytest-dev/pytest-cov/pull/435>`_. * Removed the empty `console_scripts` entrypoint that confused some Gentoo build script. I didn't ask why it was so broken cause I didn't want to ruin my day. Contributed by Michał Górny in `434 <https://github.com/pytest-dev/pytest-cov/pull/434>`_. * Fixed the missing `coverage context <https://coverage.readthedocs.io/en/stable/contexts.html>`_ when using subprocesses. Contributed by Bernát Gábor in `443 <https://github.com/pytest-dev/pytest-cov/pull/443>`_. * Updated the config section in the docs. Contributed by Pamela McA'Nulty in `429 <https://github.com/pytest-dev/pytest-cov/pull/429>`_. * Migrated CI to travis-ci.com (from .org). ``` </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> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>