[PR #80] [MERGED] Scheduled weekly dependency update for week 02 #120

New issue

Closed

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

kerem commented

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

Owner

📋 Pull Request Information

Original PR: https://github.com/jeffknupp/sandman2/pull/80
Author: @pyup-bot
Created: 1/14/2019
Status: ✅ Merged
Merged: 1/16/2019
Merged by: @jeffknupp

Base: master ← Head: pyup-scheduled-update-2019-01-14

📝 Commits (2)

df35862 Update sqlalchemy from 1.2.15 to 1.2.16
d5dc2d9 Update pytest from 4.1.0 to 4.1.1

📊 Changes

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

View changed files

📝 requirements.txt (+2 -2)

📄 Description

Update SQLAlchemy from 1.2.15 to 1.2.16.

Changelog

1.2.16

:released: January 11, 2019

 .. change::
    :tag: bug, sql
    :tickets: 4394

    Fixed issue in &quot;expanding IN&quot; feature where using the same bound parameter
    name more than once in a query would lead to a KeyError within the process
    of rewriting the parameters in the query.

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

    Fixed issue where a :class:`.postgresql.ENUM` or a custom domain present
    in a remote schema would not be recognized within column reflection if
    the name of the enum/domain or the name of the schema required quoting.
    A new parsing scheme now fully parses out quoted or non-quoted tokens
    including support for SQL-escaped quotes.

 .. change::
    :tags: bug, postgresql

    Fixed issue where multiple :class:`.postgresql.ENUM` objects referred to
    by the same :class:`.MetaData` object would fail to be created if
    multiple objects had the same name under different schema names.  The
    internal memoization the PostgreSQL dialect uses to track if it has
    created a particular :class:`.postgresql.ENUM` in the database during
    a DDL creation sequence now takes schema name into account.

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

    Fixed a regression introduced in version 1.2 where a refactor
    of the :class:`.SQLAlchemyError` base exception class introduced an
    inappropriate coercion of a plain string message into Unicode under
    python 2k, which is not handled by the Python interpreter for characters
    outside of the platform&#39;s encoding (typically ascii).  The
    :class:`.SQLAlchemyError` class now passes a bytestring through under
    Py2K for ``__str__()`` as is the behavior of exception objects in general
    under Py2K, does a safe coercion to unicode utf-8 with
    backslash fallback for ``__unicode__()``.  For Py3K the message is
    typically unicode already, but if not is again safe-coerced with utf-8
    with backslash fallback for the ``__str__()`` method.

 .. change::
    :tags: bug, sql, oracle, mysql
    :tickets: 4436

    Fixed issue where the DDL emitted for :class:`.DropTableComment`, which
    will be used by an upcoming version of Alembic, was incorrect for the MySQL
    and Oracle databases.

 .. change::
    :tags: bug, sqlite
    :tickets: 4431

    Reflection of an index based on SQL expressions are now skipped with a
    warning, in the same way as that of the Postgresql dialect, where we currently
    do not support reflecting indexes that have SQL expressions within them.
    Previously, an index with columns of None were produced which would break
    tools like Alembic.

.. changelog::

Links

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

Update pytest from 4.1.0 to 4.1.1.

Changelog

4.1.1

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

Bug Fixes
---------

- `2256 &lt;https://github.com/pytest-dev/pytest/issues/2256&gt;`_: Show full repr with ``assert a==b`` and ``-vv``.


- `3456 &lt;https://github.com/pytest-dev/pytest/issues/3456&gt;`_: Extend Doctest-modules to ignore mock objects.


- `4617 &lt;https://github.com/pytest-dev/pytest/issues/4617&gt;`_: Fixed ``pytest.warns`` bug when context manager is reused (e.g. multiple parametrization).


- `4631 &lt;https://github.com/pytest-dev/pytest/issues/4631&gt;`_: Don&#39;t rewrite assertion when ``__getattr__`` is broken



Improved Documentation
----------------------

- `3375 &lt;https://github.com/pytest-dev/pytest/issues/3375&gt;`_: Document that using ``setup.cfg`` may crash other tools or cause hard to track down problems because it uses a different parser than ``pytest.ini`` or ``tox.ini`` files.



Trivial/Internal Changes
------------------------

- `4602 &lt;https://github.com/pytest-dev/pytest/issues/4602&gt;`_: Uninstall ``hypothesis`` in regen tox env.

Links

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

_{🔄 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/80 **Author:** [@pyup-bot](https://github.com/pyup-bot) **Created:** 1/14/2019 **Status:** ✅ Merged **Merged:** 1/16/2019 **Merged by:** [@jeffknupp](https://github.com/jeffknupp) **Base:** `master` ← **Head:** `pyup-scheduled-update-2019-01-14` --- ### 📝 Commits (2) - [`df35862`](https://github.com/jeffknupp/sandman2/commit/df35862be5e3c7f0814c1a10d70386620853e86c) Update sqlalchemy from 1.2.15 to 1.2.16 - [`d5dc2d9`](https://github.com/jeffknupp/sandman2/commit/d5dc2d96c4a66a3fcd48987054bae4b3c36fa05e) Update pytest from 4.1.0 to 4.1.1 ### 📊 Changes **1 file changed** (+2 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `requirements.txt` (+2 -2) </details> ### 📄 Description ### Update [SQLAlchemy](https://pypi.org/project/SQLAlchemy) from **1.2.15** to **1.2.16**. <details> <summary>Changelog</summary> ### 1.2.16 ``` :released: January 11, 2019 .. change:: :tag: bug, sql :tickets: 4394 Fixed issue in "expanding IN" feature where using the same bound parameter name more than once in a query would lead to a KeyError within the process of rewriting the parameters in the query. .. change:: :tags: bug, postgresql :tickets: 4416 Fixed issue where a :class:`.postgresql.ENUM` or a custom domain present in a remote schema would not be recognized within column reflection if the name of the enum/domain or the name of the schema required quoting. A new parsing scheme now fully parses out quoted or non-quoted tokens including support for SQL-escaped quotes. .. change:: :tags: bug, postgresql Fixed issue where multiple :class:`.postgresql.ENUM` objects referred to by the same :class:`.MetaData` object would fail to be created if multiple objects had the same name under different schema names. The internal memoization the PostgreSQL dialect uses to track if it has created a particular :class:`.postgresql.ENUM` in the database during a DDL creation sequence now takes schema name into account. .. change:: :tags: bug, engine :tickets: 4429 Fixed a regression introduced in version 1.2 where a refactor of the :class:`.SQLAlchemyError` base exception class introduced an inappropriate coercion of a plain string message into Unicode under python 2k, which is not handled by the Python interpreter for characters outside of the platform's encoding (typically ascii). The :class:`.SQLAlchemyError` class now passes a bytestring through under Py2K for ``__str__()`` as is the behavior of exception objects in general under Py2K, does a safe coercion to unicode utf-8 with backslash fallback for ``__unicode__()``. For Py3K the message is typically unicode already, but if not is again safe-coerced with utf-8 with backslash fallback for the ``__str__()`` method. .. change:: :tags: bug, sql, oracle, mysql :tickets: 4436 Fixed issue where the DDL emitted for :class:`.DropTableComment`, which will be used by an upcoming version of Alembic, was incorrect for the MySQL and Oracle databases. .. change:: :tags: bug, sqlite :tickets: 4431 Reflection of an index based on SQL expressions are now skipped with a warning, in the same way as that of the Postgresql dialect, where we currently do not support reflecting indexes that have SQL expressions within them. Previously, an index with columns of None were produced which would break tools like Alembic. .. 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 **4.1.0** to **4.1.1**. <details> <summary>Changelog</summary> ### 4.1.1 ``` ========================= Bug Fixes --------- - `2256 <https://github.com/pytest-dev/pytest/issues/2256>`_: Show full repr with ``assert a==b`` and ``-vv``. - `3456 <https://github.com/pytest-dev/pytest/issues/3456>`_: Extend Doctest-modules to ignore mock objects. - `4617 <https://github.com/pytest-dev/pytest/issues/4617>`_: Fixed ``pytest.warns`` bug when context manager is reused (e.g. multiple parametrization). - `4631 <https://github.com/pytest-dev/pytest/issues/4631>`_: Don't rewrite assertion when ``__getattr__`` is broken Improved Documentation ---------------------- - `3375 <https://github.com/pytest-dev/pytest/issues/3375>`_: Document that using ``setup.cfg`` may crash other tools or cause hard to track down problems because it uses a different parser than ``pytest.ini`` or ``tox.ini`` files. Trivial/Internal Changes ------------------------ - `4602 <https://github.com/pytest-dev/pytest/issues/4602>`_: Uninstall ``hypothesis`` in regen tox env. ``` </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> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>