[PR #181] [CLOSED] Scheduled weekly dependency update for week 43 #206

New issue

Closed

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

kerem commented

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

Owner

📋 Pull Request Information

Original PR: https://github.com/jeffknupp/sandman2/pull/181
Author: @pyup-bot
Created: 10/26/2020
Status: ❌ Closed

Base: master ← Head: pyup-scheduled-update-2020-10-26

📝 Commits (3)

dc8fe0a Update flask-admin from 1.5.6 to 1.5.7
1aa162f Update sqlalchemy from 1.3.19 to 1.3.20
6215861 Update zipp from 3.3.0 to 3.4.0

📊 Changes

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

View changed files

📝 requirements.txt (+3 -3)

📄 Description

Update Flask-Admin from 1.5.6 to 1.5.7.

Changelog

1.5.7

-----

* Bootstrap 4 support!
* Added hook for custom SQLAlchemy models initializers
* SQLAlchemy 1.4/2.0 compatibility fix

Links

PyPI: https://pypi.org/project/flask-admin
Changelog: https://pyup.io/changelogs/flask-admin/
Repo: https://github.com/flask-admin/flask-admin/
Docs: https://pythonhosted.org/Flask-Admin/

Update SQLAlchemy from 1.3.19 to 1.3.20.

Changelog

1.3.20

:released: October 12, 2020

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

     An :class:`.ArgumentError` with more detail is now raised if the target
     parameter for :meth:`_query.Query.join` is set to an unmapped object.
     Prior to this change a less detailed ``AttributeError`` was raised.
     Pull request courtesy Ramon Williams.

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

     The &quot;skip_locked&quot; keyword used with ``with_for_update()`` will emit a
     warning when used on MariaDB backends, and will then be ignored.   This is
     a deprecated behavior that will raise in SQLAlchemy 1.4, as an application
     that requests &quot;skip locked&quot; is looking for a non-blocking operation which
     is not available on those backends.



 .. change::
     :tags: bug, engine
     :tickets: 5599

     Fixed issue where a non-string object sent to
     :class:`_exc.SQLAlchemyError` or a subclass, as occurs with some third
     party dialects, would fail to stringify correctly. Pull request
     courtesy Andrzej Bartosiński.

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

     Fixed issue where the ``pickle.dumps()`` operation against
     :class:`_expression.Over` construct would produce a recursion overflow.

 .. change::
     :tags: postgresql, usecase
     :tickets: 4392

     The psycopg2 dialect now support PostgreSQL multiple host connections, by
     passing host/port combinations to the query string. Pull request courtesy
     Ramon Williams.

     .. seealso::

         :ref:`psycopg2_multi_host`

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

     Fixed bug where an UPDATE statement against a JOIN using MySQL multi-table
     format would fail to include the table prefix for the target table if the
     statement had no WHERE clause, as only the WHERE clause were scanned to
     detect a &quot;multi table update&quot; at that particular point.  The target
     is now also scanned if it&#39;s a JOIN to get the leftmost table as the
     primary table and the additional entries as additional FROM entries.


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

     Adjusted the :meth:`_types.ARRAY.Comparator.any` and
     :meth:`_types.ARRAY.Comparator.all` methods to implement a straight &quot;NOT&quot;
     operation for negation, rather than negating the comparison operator.

 .. change::
     :tags: bug, pool
     :tickets: 5582

     Fixed issue where the following pool parameters were not being propagated
     to the new pool created when :meth:`_engine.Engine.dispose` were called:
     ``pre_ping``, ``use_lifo``.  Additionally the ``recycle`` and
     ``reset_on_return`` parameter is now propagated for the
     :class:`_engine.AssertionPool` class.

 .. change::
     :tags: bug, ext, associationproxy
     :tickets: 5541, 5542

     An informative error is now raised when attempting to use an association
     proxy element as a plain column expression to be SELECTed from or used in a
     SQL function; this use case is not currently supported.


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

     Fixed bug where an error was not raised in the case where a
     :func:`_sql.column` were added to more than one :func:`_sql.table` at a
     time.  This raised correctly for the :class:`_schema.Column` and
     :class:`_schema.Table` objects. An :class:`_exc.ArgumentError` is now
     raised when this occurs.

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

     Fixed issue where using a loader option against a string attribute name
     that is not actually a mapped attribute, such as a plain Python descriptor,
     would raise an uninformative AttributeError;  a descriptive error is now
     raised.



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

     Adjusted the MySQL dialect to correctly parenthesize functional index
     expressions as accepted by MySQL 8. Pull request courtesy Ramon Williams.

 .. change::
     :tags: bug, engine
     :tickets: 5632

     Repaired a function-level import that was not using SQLAlchemy&#39;s standard
     late-import system within the sqlalchemy.exc module.


 .. change::
     :tags: change, mysql
     :tickets: 5539

     Add new MySQL reserved words: ``cube``, ``lateral`` added in MySQL 8.0.1
     and 8.0.14, respectively; this indicates that these terms will be quoted if
     used as table or column identifier names.

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

     Fixed issue where a SQLAlchemy connection URI for Azure DW with
     ``authentication=ActiveDirectoryIntegrated`` (and no username+password)
     was not constructing the ODBC connection string in a way that was
     acceptable to the Azure DW instance.

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

     Fixed issue where the :class:`_postgresql.ENUM` type would not consult the
     schema translate map when emitting a CREATE TYPE or DROP TYPE during the
     test to see if the type exists or not.  Additionally, repaired an issue
     where if the same enum were encountered multiple times in a single DDL
     sequence, the &quot;check&quot; query would run repeatedly rather than relying upon a
     cached value.


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

     Fixed incompatibilities in the test suite when running against Pytest 6.x.


.. changelog::

Links

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

Update zipp from 3.3.0 to 3.4.0.

Changelog

3.4.0

======

68 and bpo-42090: ``Path.joinpath`` now takes arbitrary
positional arguments and no longer accepts ``add`` as a
keyword argument.

3.3.2

======

Updated project metadata including badges.

3.3.1

======

bpo-42043: Add tests capturing subclassing requirements.

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/181 **Author:** [@pyup-bot](https://github.com/pyup-bot) **Created:** 10/26/2020 **Status:** ❌ Closed **Base:** `master` ← **Head:** `pyup-scheduled-update-2020-10-26` --- ### 📝 Commits (3) - [`dc8fe0a`](https://github.com/jeffknupp/sandman2/commit/dc8fe0ad61d8e828f96ed411c1fb07cb6137c472) Update flask-admin from 1.5.6 to 1.5.7 - [`1aa162f`](https://github.com/jeffknupp/sandman2/commit/1aa162f5b5b047de990f58cad970107208975f47) Update sqlalchemy from 1.3.19 to 1.3.20 - [`6215861`](https://github.com/jeffknupp/sandman2/commit/621586152f752fea9351e18edc93382fea37b548) Update zipp from 3.3.0 to 3.4.0 ### 📊 Changes **1 file changed** (+3 additions, -3 deletions) <details> <summary>View changed files</summary> 📝 `requirements.txt` (+3 -3) </details> ### 📄 Description ### Update [Flask-Admin](https://pypi.org/project/Flask-Admin) from **1.5.6** to **1.5.7**. <details> <summary>Changelog</summary> ### 1.5.7 ``` ----- * Bootstrap 4 support! * Added hook for custom SQLAlchemy models initializers * SQLAlchemy 1.4/2.0 compatibility fix ``` </details> <details> <summary>Links</summary> - PyPI: https://pypi.org/project/flask-admin - Changelog: https://pyup.io/changelogs/flask-admin/ - Repo: https://github.com/flask-admin/flask-admin/ - Docs: https://pythonhosted.org/Flask-Admin/ </details> ### Update [SQLAlchemy](https://pypi.org/project/SQLAlchemy) from **1.3.19** to **1.3.20**. <details> <summary>Changelog</summary> ### 1.3.20 ``` :released: October 12, 2020 .. change:: :tags: bug, orm :tickets: 4428 An :class:`.ArgumentError` with more detail is now raised if the target parameter for :meth:`_query.Query.join` is set to an unmapped object. Prior to this change a less detailed ``AttributeError`` was raised. Pull request courtesy Ramon Williams. .. change:: :tags: bug, mysql :tickets: 5568 The "skip_locked" keyword used with ``with_for_update()`` will emit a warning when used on MariaDB backends, and will then be ignored. This is a deprecated behavior that will raise in SQLAlchemy 1.4, as an application that requests "skip locked" is looking for a non-blocking operation which is not available on those backends. .. change:: :tags: bug, engine :tickets: 5599 Fixed issue where a non-string object sent to :class:`_exc.SQLAlchemyError` or a subclass, as occurs with some third party dialects, would fail to stringify correctly. Pull request courtesy Andrzej Bartosiński. .. change:: :tags: bug, sql :tickets: 5644 Fixed issue where the ``pickle.dumps()`` operation against :class:`_expression.Over` construct would produce a recursion overflow. .. change:: :tags: postgresql, usecase :tickets: 4392 The psycopg2 dialect now support PostgreSQL multiple host connections, by passing host/port combinations to the query string. Pull request courtesy Ramon Williams. .. seealso:: :ref:`psycopg2_multi_host` .. change:: :tags: bug, mysql :tickets: 5617 Fixed bug where an UPDATE statement against a JOIN using MySQL multi-table format would fail to include the table prefix for the target table if the statement had no WHERE clause, as only the WHERE clause were scanned to detect a "multi table update" at that particular point. The target is now also scanned if it's a JOIN to get the leftmost table as the primary table and the additional entries as additional FROM entries. .. change:: :tags: bug, postgresql :tickets: 5518 Adjusted the :meth:`_types.ARRAY.Comparator.any` and :meth:`_types.ARRAY.Comparator.all` methods to implement a straight "NOT" operation for negation, rather than negating the comparison operator. .. change:: :tags: bug, pool :tickets: 5582 Fixed issue where the following pool parameters were not being propagated to the new pool created when :meth:`_engine.Engine.dispose` were called: ``pre_ping``, ``use_lifo``. Additionally the ``recycle`` and ``reset_on_return`` parameter is now propagated for the :class:`_engine.AssertionPool` class. .. change:: :tags: bug, ext, associationproxy :tickets: 5541, 5542 An informative error is now raised when attempting to use an association proxy element as a plain column expression to be SELECTed from or used in a SQL function; this use case is not currently supported. .. change:: :tags: bug, sql :tickets: 5618 Fixed bug where an error was not raised in the case where a :func:`_sql.column` were added to more than one :func:`_sql.table` at a time. This raised correctly for the :class:`_schema.Column` and :class:`_schema.Table` objects. An :class:`_exc.ArgumentError` is now raised when this occurs. .. change:: :tags: bug, orm :tickets: 4589 Fixed issue where using a loader option against a string attribute name that is not actually a mapped attribute, such as a plain Python descriptor, would raise an uninformative AttributeError; a descriptive error is now raised. .. change:: :tags: mysql, usecase :tickets: 5462 Adjusted the MySQL dialect to correctly parenthesize functional index expressions as accepted by MySQL 8. Pull request courtesy Ramon Williams. .. change:: :tags: bug, engine :tickets: 5632 Repaired a function-level import that was not using SQLAlchemy's standard late-import system within the sqlalchemy.exc module. .. change:: :tags: change, mysql :tickets: 5539 Add new MySQL reserved words: ``cube``, ``lateral`` added in MySQL 8.0.1 and 8.0.14, respectively; this indicates that these terms will be quoted if used as table or column identifier names. .. change:: :tags: bug, mssql :tickets: 5592 Fixed issue where a SQLAlchemy connection URI for Azure DW with ``authentication=ActiveDirectoryIntegrated`` (and no username+password) was not constructing the ODBC connection string in a way that was acceptable to the Azure DW instance. .. change:: :tags: bug, postgresql :tickets: 5520 Fixed issue where the :class:`_postgresql.ENUM` type would not consult the schema translate map when emitting a CREATE TYPE or DROP TYPE during the test to see if the type exists or not. Additionally, repaired an issue where if the same enum were encountered multiple times in a single DDL sequence, the "check" query would run repeatedly rather than relying upon a cached value. .. change:: :tags: bug, tests :tickets: 5635 Fixed incompatibilities in the test suite when running against Pytest 6.x. .. 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 [zipp](https://pypi.org/project/zipp) from **3.3.0** to **3.4.0**. <details> <summary>Changelog</summary> ### 3.4.0 ``` ====== 68 and bpo-42090: ``Path.joinpath`` now takes arbitrary positional arguments and no longer accepts ``add`` as a keyword argument. ``` ### 3.3.2 ``` ====== Updated project metadata including badges. ``` ### 3.3.1 ``` ====== bpo-42043: Add tests capturing subclassing requirements. ``` </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>