starred/sandman2-jeffknupp
1
0
Fork 0
mirror of https://github.com/jeffknupp/sandman2.git synced 2026-04-25 16:45:50 +03:00
Code Issues 45 Projects Releases Packages Wiki Activity

[PR #203] [CLOSED] Scheduled weekly dependency update for week 09 #224

New issue
Closed
opened 2026-02-26 01:33:40 +03:00 by kerem · 0 comments
kerem commented 2026-02-26 01:33:40 +03:00
Owner
Copy link

📋 Pull Request Information

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

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

📝 Commits (6)

  • ca51913 Update sqlalchemy from 1.3.20 to 1.3.23
  • aefcf9c Update coverage from 5.3 to 5.5
  • 3b824ee Update pytest from 6.2.0 to 6.2.2
  • 3eda9e5 Update flask-cors from 3.0.9 to 3.0.10
  • 1922932 Update pytest-cov from 2.10.1 to 2.11.1
  • 1ac8c6b Update pytest-flask from 1.1.0 to 1.2.0

📊 Changes

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

View changed files

📝 requirements.txt (+6 -6)

📄 Description

Update SQLAlchemy from 1.3.20 to 1.3.23.

Changelog

1.3.23

:released: February 1, 2021

 .. change::
     :tags: bug, ext
     :tickets: 5836

     Fixed issue where the stringification that is sometimes called when
     attempting to generate the "key" for the ``.c`` collection on a selectable
     would fail if the column were an unlabeled custom SQL construct using the
     ``sqlalchemy.ext.compiler`` extension, and did not provide a default
     compilation form; while this seems like an unusual case, it can get invoked
     for some ORM scenarios such as when the expression is used in an "order by"
     in combination with joined eager loading.  The issue is that the lack of a
     default compiler function was raising :class:`.CompileError` and not
     :class:`.UnsupportedCompilationError`.

 .. change::
     :tags: bug, postgresql
     :tickets: 5645

     For SQLAlchemy 1.3 only, setup.py pins pg8000 to a version lower than
     1.16.6. Version 1.16.6 and above is supported by SQLAlchemy 1.4. Pull
     request courtesy Giuseppe Lumia.

 .. change::
     :tags: bug, postgresql
     :tickets: 5850

     Fixed issue where using :meth:`_schema.Table.to_metadata` (called
     :meth:`_schema.Table.tometadata` in 1.3) in conjunction with a PostgreSQL
     :class:`_postgresql.ExcludeConstraint` that made use of ad-hoc column
     expressions would fail to copy correctly.

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

     Fixed bug where making use of the :meth:`.TypeEngine.with_variant` method
     on a :class:`.TypeDecorator` type would fail to take into account the
     dialect-specific mappings in use, due to a rule in :class:`.TypeDecorator`
     that was instead attempting to check for chains of :class:`.TypeDecorator`
     instances.


 .. change::
     :tags: bug, mysql, reflection
     :tickets: 5860

     Fixed bug where MySQL server default reflection would fail for numeric
     values with a negation symbol present.


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

     Fixed regression in Oracle dialect introduced by :ticket:`4894` in
     SQLAlchemy 1.3.11 where use of a SQL expression in RETURNING for an UPDATE
     would fail to compile, due to a check for "server_default" when an
     arbitrary SQL expression is not a column.


 .. change::
     :tags: usecase, mysql
     :tickets: 5808

     Casting to ``FLOAT`` is now supported in MySQL >= (8, 0, 17) and
     MariaDb >= (10, 4, 5).

 .. change::
     :tags: bug, mysql
     :tickets: 5898

     Fixed long-lived bug in MySQL dialect where the maximum identifier length
     of 255 was too long for names of all types of constraints, not just
     indexes, all of which have a size limit of 64. As metadata naming
     conventions can create too-long names in this area, apply the limit to the
     identifier generator within the DDL compiler.

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

     Fixed bug in Oracle dialect where retriving a CLOB/BLOB column via
     :meth:`_dml.Insert.returning` would fail as the LOB value would need to be
     read when returned; additionally, repaired support for retrieval of Unicode
     values via RETURNING under Python 2.

 .. change::
     :tags: bug, mysql
     :tickets: 5821

     Fixed deprecation warnings that arose as a result of the release of PyMySQL
     1.0, including deprecation warnings for the "db" and "passwd" parameters
     now replaced with "database" and "password".


 .. change::
     :tags: bug, mysql
     :tickets: 5800

     Fixed regression from SQLAlchemy 1.3.20 caused by the fix for
     :ticket:`5462` which adds double-parenthesis for MySQL functional
     expressions in indexes, as is required by the backend, this inadvertently
     extended to include arbitrary :func:`_sql.text` expressions as well as
     Alembic's internal textual component,  which are required by Alembic for
     arbitrary index expressions which don't imply double parenthesis.  The
     check has been narrowed to include only binary/ unary/functional
     expressions directly.

.. 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'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::
Links

Update coverage from 5.3 to 5.5.

Changelog

5.5

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

- ``coverage combine`` has a new option, ``--keep`` to keep the original data
files after combining them.  The default is still to delete the files after
they have been combined.  This was requested in `issue 1108`_ and implemented
in `pull request 1110`_.  Thanks, Éric Larivière.

- When reporting missing branches in ``coverage report``, branches aren't
reported that jump to missing lines.  This adds to the long-standing behavior
of not reporting branches from missing lines.  Now branches are only reported
if both the source and destination lines are executed.  Closes both `issue
1065`_ and `issue 955`_.

- Minor improvements to the HTML report:

- The state of the line visibility selector buttons is saved in local storage
 so you don't have to fiddle with them so often, fixing `issue 1123`_.

- It has a little more room for line numbers so that 4-digit numbers work
 well, fixing `issue 1124`_.

- Improved the error message when combining line and branch data, so that users
will be more likely to understand what's happening, closing `issue 803`_.

.. _issue 803: https://github.com/nedbat/coveragepy/issues/803
.. _issue 955: https://github.com/nedbat/coveragepy/issues/955
.. _issue 1065: https://github.com/nedbat/coveragepy/issues/1065
.. _issue 1108: https://github.com/nedbat/coveragepy/issues/1108
.. _pull request 1110: https://github.com/nedbat/coveragepy/pull/1110
.. _issue 1123: https://github.com/nedbat/coveragepy/issues/1123
.. _issue 1124: https://github.com/nedbat/coveragepy/issues/1124


.. _changes_54:

5.4

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

- The text report produced by ``coverage report`` now always outputs a TOTAL
line, even if only one Python file is reported.  This makes regex parsing
of the output easier.  Thanks, Judson Neer.  This had been requested a number
of times (`issue 1086`_, `issue 922`_, `issue 732`_).

- The ``skip_covered`` and ``skip_empty`` settings in the configuration file
can now be specified in the ``[html]`` section, so that text reports and HTML
reports can use separate settings.  The HTML report will still use the
``[report]`` settings if there isn't a value in the ``[html]`` section.
Closes `issue 1090`_.

- Combining files on Windows across drives now works properly, fixing `issue
577`_.  Thanks, `Valentin Lab <pr1080_>`_.

- Fix an obscure warning from deep in the _decimal module, as reported in
`issue 1084`_.

- Update to support Python 3.10 alphas in progress, including `PEP 626: Precise
line numbers for debugging and other tools <pep626_>`_.

.. _issue 577: https://github.com/nedbat/coveragepy/issues/577
.. _issue 732: https://github.com/nedbat/coveragepy/issues/732
.. _issue 922: https://github.com/nedbat/coveragepy/issues/922
.. _issue 1084: https://github.com/nedbat/coveragepy/issues/1084
.. _issue 1086: https://github.com/nedbat/coveragepy/issues/1086
.. _issue 1090: https://github.com/nedbat/coveragepy/issues/1090
.. _pr1080: https://github.com/nedbat/coveragepy/pull/1080
.. _pep626: https://www.python.org/dev/peps/pep-0626/


.. _changes_531:

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:
Links

Update pytest from 6.2.0 to 6.2.2.

Changelog

6.2.2

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

Bug Fixes
---------

- `8152 <https://github.com/pytest-dev/pytest/issues/8152>`_: Fixed "(<Skipped instance>)" being shown as a skip reason in the verbose test summary line when the reason is empty.


- `8249 <https://github.com/pytest-dev/pytest/issues/8249>`_: Fix the ``faulthandler`` plugin for occasions when running with ``twisted.logger`` and using ``pytest --capture=no``.

6.2.1

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

Bug Fixes
---------

- `7678 <https://github.com/pytest-dev/pytest/issues/7678>`_: Fixed bug where ``ImportPathMismatchError`` would be raised for files compiled in
the host and loaded later from an UNC mounted path (Windows).


- `8132 <https://github.com/pytest-dev/pytest/issues/8132>`_: Fixed regression in ``approx``: in 6.2.0 ``approx`` no longer raises
``TypeError`` when dealing with non-numeric types, falling back to normal comparison.
Before 6.2.0, array types like tf.DeviceArray fell through to the scalar case,
and happened to compare correctly to a scalar if they had only one element.
After 6.2.0, these types began failing, because they inherited neither from
standard Python number hierarchy nor from ``numpy.ndarray``.

``approx`` now converts arguments to ``numpy.ndarray`` if they expose the array
protocol and are not scalars. This treats array-like objects like numpy arrays,
regardless of size.
Links

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

Update pytest-cov from 2.10.1 to 2.11.1.

Changelog

2.11.1

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

* Fixed support for newer setuptools (v42+).
Contributed by Michał Górny in `451 <https://github.com/pytest-dev/pytest-cov/pull/451>`_.

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).
Links

Update pytest-flask from 1.1.0 to 1.2.0.

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

Links

🔄 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/203 **Author:** [@pyup-bot](https://github.com/pyup-bot) **Created:** 3/1/2021 **Status:** ❌ Closed **Base:** `master` ← **Head:** `pyup-scheduled-update-2021-03-01` --- ### 📝 Commits (6) - [`ca51913`](https://github.com/jeffknupp/sandman2/commit/ca51913232975ce22033d34783e47d57902c3938) Update sqlalchemy from 1.3.20 to 1.3.23 - [`aefcf9c`](https://github.com/jeffknupp/sandman2/commit/aefcf9c1ebf2792a52170641ad657fadf7bb344c) Update coverage from 5.3 to 5.5 - [`3b824ee`](https://github.com/jeffknupp/sandman2/commit/3b824ee38f71e5461eea187243122d75d121d156) Update pytest from 6.2.0 to 6.2.2 - [`3eda9e5`](https://github.com/jeffknupp/sandman2/commit/3eda9e55ead6c03d78700678d8b3204db385b059) Update flask-cors from 3.0.9 to 3.0.10 - [`1922932`](https://github.com/jeffknupp/sandman2/commit/19229321fd198c852ff2302a7ea2a068f2712942) Update pytest-cov from 2.10.1 to 2.11.1 - [`1ac8c6b`](https://github.com/jeffknupp/sandman2/commit/1ac8c6b693d528f79b0ee02fb1378afaaa9c0fb1) Update pytest-flask from 1.1.0 to 1.2.0 ### 📊 Changes **1 file changed** (+6 additions, -6 deletions) <details> <summary>View changed files</summary> 📝 `requirements.txt` (+6 -6) </details> ### 📄 Description ### Update [SQLAlchemy](https://pypi.org/project/SQLAlchemy) from **1.3.20** to **1.3.23**. <details> <summary>Changelog</summary> ### 1.3.23 ``` :released: February 1, 2021 .. change:: :tags: bug, ext :tickets: 5836 Fixed issue where the stringification that is sometimes called when attempting to generate the &quot;key&quot; for the ``.c`` collection on a selectable would fail if the column were an unlabeled custom SQL construct using the ``sqlalchemy.ext.compiler`` extension, and did not provide a default compilation form; while this seems like an unusual case, it can get invoked for some ORM scenarios such as when the expression is used in an &quot;order by&quot; in combination with joined eager loading. The issue is that the lack of a default compiler function was raising :class:`.CompileError` and not :class:`.UnsupportedCompilationError`. .. change:: :tags: bug, postgresql :tickets: 5645 For SQLAlchemy 1.3 only, setup.py pins pg8000 to a version lower than 1.16.6. Version 1.16.6 and above is supported by SQLAlchemy 1.4. Pull request courtesy Giuseppe Lumia. .. change:: :tags: bug, postgresql :tickets: 5850 Fixed issue where using :meth:`_schema.Table.to_metadata` (called :meth:`_schema.Table.tometadata` in 1.3) in conjunction with a PostgreSQL :class:`_postgresql.ExcludeConstraint` that made use of ad-hoc column expressions would fail to copy correctly. .. change:: :tags: bug, sql :tickets: 5816 Fixed bug where making use of the :meth:`.TypeEngine.with_variant` method on a :class:`.TypeDecorator` type would fail to take into account the dialect-specific mappings in use, due to a rule in :class:`.TypeDecorator` that was instead attempting to check for chains of :class:`.TypeDecorator` instances. .. change:: :tags: bug, mysql, reflection :tickets: 5860 Fixed bug where MySQL server default reflection would fail for numeric values with a negation symbol present. .. change:: :tags: bug, oracle :tickets: 5813 Fixed regression in Oracle dialect introduced by :ticket:`4894` in SQLAlchemy 1.3.11 where use of a SQL expression in RETURNING for an UPDATE would fail to compile, due to a check for &quot;server_default&quot; when an arbitrary SQL expression is not a column. .. change:: :tags: usecase, mysql :tickets: 5808 Casting to ``FLOAT`` is now supported in MySQL &gt;= (8, 0, 17) and MariaDb &gt;= (10, 4, 5). .. change:: :tags: bug, mysql :tickets: 5898 Fixed long-lived bug in MySQL dialect where the maximum identifier length of 255 was too long for names of all types of constraints, not just indexes, all of which have a size limit of 64. As metadata naming conventions can create too-long names in this area, apply the limit to the identifier generator within the DDL compiler. .. change:: :tags: bug, oracle :tickets: 5812 Fixed bug in Oracle dialect where retriving a CLOB/BLOB column via :meth:`_dml.Insert.returning` would fail as the LOB value would need to be read when returned; additionally, repaired support for retrieval of Unicode values via RETURNING under Python 2. .. change:: :tags: bug, mysql :tickets: 5821 Fixed deprecation warnings that arose as a result of the release of PyMySQL 1.0, including deprecation warnings for the &quot;db&quot; and &quot;passwd&quot; parameters now replaced with &quot;database&quot; and &quot;password&quot;. .. change:: :tags: bug, mysql :tickets: 5800 Fixed regression from SQLAlchemy 1.3.20 caused by the fix for :ticket:`5462` which adds double-parenthesis for MySQL functional expressions in indexes, as is required by the backend, this inadvertently extended to include arbitrary :func:`_sql.text` expressions as well as Alembic&#39;s internal textual component, which are required by Alembic for arbitrary index expressions which don&#39;t imply double parenthesis. The check has been narrowed to include only binary/ unary/functional expressions directly. .. 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:: ``` </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.5**. <details> <summary>Changelog</summary> ### 5.5 ``` -------------------------- - ``coverage combine`` has a new option, ``--keep`` to keep the original data files after combining them. The default is still to delete the files after they have been combined. This was requested in `issue 1108`_ and implemented in `pull request 1110`_. Thanks, Éric Larivière. - When reporting missing branches in ``coverage report``, branches aren&#39;t reported that jump to missing lines. This adds to the long-standing behavior of not reporting branches from missing lines. Now branches are only reported if both the source and destination lines are executed. Closes both `issue 1065`_ and `issue 955`_. - Minor improvements to the HTML report: - The state of the line visibility selector buttons is saved in local storage so you don&#39;t have to fiddle with them so often, fixing `issue 1123`_. - It has a little more room for line numbers so that 4-digit numbers work well, fixing `issue 1124`_. - Improved the error message when combining line and branch data, so that users will be more likely to understand what&#39;s happening, closing `issue 803`_. .. _issue 803: https://github.com/nedbat/coveragepy/issues/803 .. _issue 955: https://github.com/nedbat/coveragepy/issues/955 .. _issue 1065: https://github.com/nedbat/coveragepy/issues/1065 .. _issue 1108: https://github.com/nedbat/coveragepy/issues/1108 .. _pull request 1110: https://github.com/nedbat/coveragepy/pull/1110 .. _issue 1123: https://github.com/nedbat/coveragepy/issues/1123 .. _issue 1124: https://github.com/nedbat/coveragepy/issues/1124 .. _changes_54: ``` ### 5.4 ``` -------------------------- - The text report produced by ``coverage report`` now always outputs a TOTAL line, even if only one Python file is reported. This makes regex parsing of the output easier. Thanks, Judson Neer. This had been requested a number of times (`issue 1086`_, `issue 922`_, `issue 732`_). - The ``skip_covered`` and ``skip_empty`` settings in the configuration file can now be specified in the ``[html]`` section, so that text reports and HTML reports can use separate settings. The HTML report will still use the ``[report]`` settings if there isn&#39;t a value in the ``[html]`` section. Closes `issue 1090`_. - Combining files on Windows across drives now works properly, fixing `issue 577`_. Thanks, `Valentin Lab &lt;pr1080_&gt;`_. - Fix an obscure warning from deep in the _decimal module, as reported in `issue 1084`_. - Update to support Python 3.10 alphas in progress, including `PEP 626: Precise line numbers for debugging and other tools &lt;pep626_&gt;`_. .. _issue 577: https://github.com/nedbat/coveragepy/issues/577 .. _issue 732: https://github.com/nedbat/coveragepy/issues/732 .. _issue 922: https://github.com/nedbat/coveragepy/issues/922 .. _issue 1084: https://github.com/nedbat/coveragepy/issues/1084 .. _issue 1086: https://github.com/nedbat/coveragepy/issues/1086 .. _issue 1090: https://github.com/nedbat/coveragepy/issues/1090 .. _pr1080: https://github.com/nedbat/coveragepy/pull/1080 .. _pep626: https://www.python.org/dev/peps/pep-0626/ .. _changes_531: ``` ### 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: ``` </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.2**. <details> <summary>Changelog</summary> ### 6.2.2 ``` ========================= Bug Fixes --------- - `8152 &lt;https://github.com/pytest-dev/pytest/issues/8152&gt;`_: Fixed &quot;(&lt;Skipped instance&gt;)&quot; being shown as a skip reason in the verbose test summary line when the reason is empty. - `8249 &lt;https://github.com/pytest-dev/pytest/issues/8249&gt;`_: Fix the ``faulthandler`` plugin for occasions when running with ``twisted.logger`` and using ``pytest --capture=no``. ``` ### 6.2.1 ``` ========================= Bug Fixes --------- - `7678 &lt;https://github.com/pytest-dev/pytest/issues/7678&gt;`_: Fixed bug where ``ImportPathMismatchError`` would be raised for files compiled in the host and loaded later from an UNC mounted path (Windows). - `8132 &lt;https://github.com/pytest-dev/pytest/issues/8132&gt;`_: Fixed regression in ``approx``: in 6.2.0 ``approx`` no longer raises ``TypeError`` when dealing with non-numeric types, falling back to normal comparison. Before 6.2.0, array types like tf.DeviceArray fell through to the scalar case, and happened to compare correctly to a scalar if they had only one element. After 6.2.0, these types began failing, because they inherited neither from standard Python number hierarchy nor from ``numpy.ndarray``. ``approx`` now converts arguments to ``numpy.ndarray`` if they expose the array protocol and are not scalars. This treats array-like objects like numpy arrays, regardless of size. ``` </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 [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.1**. <details> <summary>Changelog</summary> ### 2.11.1 ``` ------------------- * Fixed support for newer setuptools (v42+). Contributed by Michał Górny in `451 &lt;https://github.com/pytest-dev/pytest-cov/pull/451&gt;`_. ``` ### 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). ``` </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 [pytest-flask](https://pypi.org/project/pytest-flask) from **1.1.0** to **1.2.0**. *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-flask - Repo: https://github.com/pytest-dev/pytest-flask </details> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
kerem 2026-02-26 01:33:40 +03:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
pyup-scheduled-update-2026-04-20
pyup-scheduled-update-2024-09-16
pyup-scheduled-update-2023-07-24
pyup-scheduled-update-2023-06-19
pyup-scheduled-update-2023-05-22
pyup-scheduled-update-2023-05-15
pyup-scheduled-update-2023-05-08
dependabot/pip/flask-2.3.2
pyup-scheduled-update-2023-05-01
pyup-scheduled-update-2023-04-03
dependabot/pip/werkzeug-2.2.3
pyup-scheduled-update-2022-11-14
pyup-scheduled-update-2022-10-03
pyup-scheduled-update-2022-08-01
pyup-scheduled-update-2022-06-13
pyup-scheduled-update-2022-05-30
pyup-scheduled-update-2022-03-07
pyup-scheduled-update-2022-01-10
pyup-scheduled-update-2021-11-01
pyup-scheduled-update-2020-10-05
pyup-scheduled-update-2019-09-30
pyup-scheduled-update-2019-07-29
pyup-scheduled-update-2019-07-22
pyup-scheduled-update-2019-05-27
pyup-scheduled-update-2019-03-11
marshmallow
pyup-scheduled-update-2019-02-25
pyup-scheduled-update-2019-02-18
pyup-scheduled-update-2019-01-28
pyup-scheduled-update-2019-01-14
docker
name-map-stupid
swagger
fix-pagination
doc-expansion
specify-schema
No results found.
Labels
Clear labels   
bug

   
duplicate

   
enhancement

   
help wanted

   
invalid

   
pull-request

Mirrored from GitHub Pull Request

  
question

   
refactoring

   
research

   
wontfix
No labels
bug
duplicate
enhancement
help wanted
invalid
pull-request
question
refactoring
research
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/sandman2-jeffknupp#224
No description provided.