Bump the python-packages group with 8 updates

[dependabot]

Bumps the python-packages group with 8 updates:

Package	From	To
psycopg2	2.9.6	2.9.9
sqlalchemy	2.0.13	2.0.28
black	23.10.1	24.2.0
pytest	7.4.2	8.1.1
pytest-asyncio	0.21.0	0.23.5.post1
pylint	3.0.2	3.1.0
mypy	1.6.0	1.9.0
types-pyyaml	6.0.12.12	6.0.12.20240311

Updates psycopg2 from 2.9.6 to 2.9.9

Changelog

Sourced from psycopg2's changelog.

Current release

What's new in psycopg 2.9.9 ^^^^^^^^^^^^^^^^^^^^^^^^^^^

• Add support for Python 3.12.
• Drop support for Python 3.6.

What's new in psycopg 2.9.8 ^^^^^^^^^^^^^^^^^^^^^^^^^^^

• Wheel package bundled with PostgreSQL 16 libpq in order to add support for recent features, such as sslcertmode.

What's new in psycopg 2.9.7 ^^^^^^^^^^^^^^^^^^^^^^^^^^^

• Fix propagation of exceptions raised during module initialization (:ticket:[#1598](https://github.com/psycopg/psycopg2/issues/1598)).
• Fix building when pg_config returns an empty string (:ticket:[#1599](https://github.com/psycopg/psycopg2/issues/1599)).
• Wheel package bundled with OpenSSL 1.1.1v.

What's new in psycopg 2.9.6 ^^^^^^^^^^^^^^^^^^^^^^^^^^^

• Package manylinux 2014 for aarch64 and ppc64le platforms, in order to include libpq 15 in the binary package (:ticket:[#1396](https://github.com/psycopg/psycopg2/issues/1396)).
• Wheel package bundled with OpenSSL 1.1.1t.

What's new in psycopg 2.9.5 ^^^^^^^^^^^^^^^^^^^^^^^^^^^

• Add support for Python 3.11.
• Add support for rowcount in MERGE statements in binary packages (:ticket:[#1497](https://github.com/psycopg/psycopg2/issues/1497)).
• Wheel package bundled with OpenSSL 1.1.1r and PostgreSQL 15 libpq.

What's new in psycopg 2.9.4 ^^^^^^^^^^^^^^^^^^^^^^^^^^^

• Fix ~psycopg2.extras.register_composite(), ~psycopg2.extras.register_range() with customized :sql:search_path (:ticket:[#1487](https://github.com/psycopg/psycopg2/issues/1487)).
• Handle correctly composite types with names or in schemas requiring escape.

... (truncated)

Commits

• ad5bee7 chore: bump version number to 2.9.9
• 37d1de1 chore: add support for Python 3.12
• abf2723 chore: drop support for Python 3.6
• 2da65a7 chore: drop leftover Python 2.7 import aliases from setup.py
• 3fa60fd chore: bump doc requirement complained by dependabot
• 1c1484e ci: better interaction with scaleway build server
• c81cec6 chore: bump to next dev release
• 7fe8cb7 chore: bump docs requirements dependabot complains about
• b39d5d6 chore: bundle libpq 16
• 921510d docs: replace "compiled against" with "bundled with" in news file
• Additional commits viewable in compare view

Updates sqlalchemy from 2.0.13 to 2.0.28

Release notes

Sourced from sqlalchemy's releases.

2.0.28

Released: March 4, 2024

orm

• [orm] [performance] [bug] [regression] Adjusted the fix made in #10570, released in 2.0.23, where new logic was added to reconcile possibly changing bound parameter values across cache key generations used within the _orm.with_expression() construct. The new logic changes the approach by which the new bound parameter values are associated with the statement, avoiding the need to deep-copy the statement which can result in a significant performance penalty for very deep / complex SQL constructs. The new approach no longer requires this deep-copy step.

  References: #11085

• [orm] [bug] [regression] Fixed regression caused by #9779 where using the "secondary" table in a relationship and_() expression would fail to be aliased to match how the "secondary" table normally renders within a _sql.Select.join() expression, leading to an invalid query.

  References: #11010

engine

• [engine] [usecase] Added new core execution option _engine.Connection.execution_options.preserve_rowcount. When set, the cursor.rowcount attribute from the DBAPI cursor will be unconditionally memoized at statement execution time, so that whatever value the DBAPI offers for any kind of statement will be available using the _engine.CursorResult.rowcount attribute from the _engine.CursorResult. This allows the rowcount to be accessed for statments such as INSERT and SELECT, to the degree supported by the DBAPI in use. The engine_insertmanyvalues also supports this option and will ensure _engine.CursorResult.rowcount is correctly set for a bulk INSERT of rows when set.

  References: #10974

asyncio

• [asyncio] [bug] An error is raised if a QueuePool or other non-asyncio pool class is passed to _asyncio.create_async_engine(). This engine only accepts asyncio-compatible pool classes including AsyncAdaptedQueuePool. Other pool classes such as NullPool are compatible with both synchronous and asynchronous

... (truncated)

Commits

• See full diff in compare view

Updates black from 23.10.1 to 24.2.0

Release notes

Sourced from black's releases.

24.2.0

Stable style

• Fixed a bug where comments where mistakenly removed along with redundant parentheses (#4218)

Preview style

• Move the hug_parens_with_braces_and_square_brackets feature to the unstable style due to an outstanding crash and proposed formatting tweaks (#4198)
• Fixed a bug where base expressions caused inconsistent formatting of ** in tenary expression (#4154)
• Checking for newline before adding one on docstring that is almost at the line limit (#4185)
• Remove redundant parentheses in case statement if guards (#4214).

Configuration

• Fix issue where Black would ignore input files in the presence of symlinks (#4222)
• Black now ignores pyproject.toml that is missing a tool.black section when discovering project root and configuration. Since Black continues to use version control as an indicator of project root, this is expected to primarily change behavior for users in a monorepo setup (desirably). If you wish to preserve previous behavior, simply add an empty [tool.black] to the previously discovered pyproject.toml (#4204)

Output

• Black will swallow any SyntaxWarnings or DeprecationWarnings produced by the ast module when performing equivalence checks (#4189)

Integrations

• Add a JSONSchema and provide a validate-pyproject entry-point (#4181)

24.1.1

Bugfix release to fix a bug that made Black unusable on certain file systems with strict limits on path length.

Preview style

• Consistently add trailing comma on typed parameters (#4164)

Configuration

• Shorten the length of the name of the cache file to fix crashes on file systems that do not support long paths (#4176)

... (truncated)

Changelog

Sourced from black's changelog.

24.2.0

Stable style

• Fixed a bug where comments where mistakenly removed along with redundant parentheses (#4218)

Preview style

• Move the hug_parens_with_braces_and_square_brackets feature to the unstable style due to an outstanding crash and proposed formatting tweaks (#4198)
• Fixed a bug where base expressions caused inconsistent formatting of ** in tenary expression (#4154)
• Checking for newline before adding one on docstring that is almost at the line limit (#4185)
• Remove redundant parentheses in case statement if guards (#4214).

Configuration

• Fix issue where Black would ignore input files in the presence of symlinks (#4222)
• Black now ignores pyproject.toml that is missing a tool.black section when discovering project root and configuration. Since Black continues to use version control as an indicator of project root, this is expected to primarily change behavior for users in a monorepo setup (desirably). If you wish to preserve previous behavior, simply add an empty [tool.black] to the previously discovered pyproject.toml (#4204)

Output

• Black will swallow any SyntaxWarnings or DeprecationWarnings produced by the ast module when performing equivalence checks (#4189)

Integrations

• Add a JSONSchema and provide a validate-pyproject entry-point (#4181)

24.1.1

Bugfix release to fix a bug that made Black unusable on certain file systems with strict limits on path length.

Preview style

• Consistently add trailing comma on typed parameters (#4164)

Configuration

• Shorten the length of the name of the cache file to fix crashes on file systems that do not support long paths (#4176)

... (truncated)

Commits

• 6fdf8a4 Prepare release 24.2.0 (#4226)
• 8af4394 fix: Don't remove comments along with parens (#4218)
• 35e9776 Bump pre-commit/action from 3.0.0 to 3.0.1 (#4225)
• 23dfc5b Fix ignoring input files for symlink reasons (#4222)
• a201003 Simplify check for symlinks that resolve outside root (#4221)
• dab37a6 Remove redundant parentheses in case statement if guards (#4214)
• 32230e6 fix: bug where the doublestar operation had inconsistent formatting. (#4154)
• 7edb50f fix: additional newline added to docstring when the previous line length is l...
• 3e80de3 Bump furo from 2023.9.10 to 2024.1.29 in /docs (#4211)
• a08b480 Bump pypa/cibuildwheel from 2.16.4 to 2.16.5 (#4212)
• Additional commits viewable in compare view

Updates pytest from 7.4.2 to 8.1.1

Release notes

Sourced from pytest's releases.

8.1.1

pytest 8.1.1 (2024-03-08)

::: {.note} ::: {.title} Note :::

This release is not a usual bug fix release -- it contains features and improvements, being a follow up to 8.1.0, which has been yanked from PyPI. :::

Features

• #11475: Added the new consider_namespace_packages{.interpreted-text role="confval"} configuration option, defaulting to False.

  If set to True, pytest will attempt to identify modules that are part of namespace packages when importing modules.

• #11653: Added the new verbosity_test_cases{.interpreted-text role="confval"} configuration option for fine-grained control of test execution verbosity. See Fine-grained verbosity <pytest.fine_grained_verbosity>{.interpreted-text role="ref"} for more details.

Improvements

• #10865: pytest.warns{.interpreted-text role="func"} now validates that warnings.warn{.interpreted-text role="func"} was called with a [str]{.title-ref} or a [Warning]{.title-ref}. Currently in Python it is possible to use other types, however this causes an exception when warnings.filterwarnings{.interpreted-text role="func"} is used to filter those warnings (see [CPython #103577](python/cpython#103577) for a discussion). While this can be considered a bug in CPython, we decided to put guards in pytest as the error message produced without this check in place is confusing.

• #11311: When using --override-ini for paths in invocations without a configuration file defined, the current working directory is used as the relative directory.

  Previoulsy this would raise an AssertionError{.interpreted-text role="class"}.

• #11475: --import-mode=importlib <import-mode-importlib>{.interpreted-text role="ref"} now tries to import modules using the standard import mechanism (but still without changing :pysys.path{.interpreted-text role="data"}), falling back to importing modules directly only if that fails.

  This means that installed packages will be imported under their canonical name if possible first, for example app.core.models, instead of having the module name always be derived from their path (for example .env310.lib.site_packages.app.core.models).

• #11801: Added the iter_parents() <_pytest.nodes.Node.iter_parents>{.interpreted-text role="func"} helper method on nodes. It is similar to listchain <_pytest.nodes.Node.listchain>{.interpreted-text role="func"}, but goes from bottom to top, and returns an iterator, not a list.

• #11850: Added support for sys.last_exc{.interpreted-text role="data"} for post-mortem debugging on Python>=3.12.

• #11962: In case no other suitable candidates for configuration file are found, a pyproject.toml (even without a [tool.pytest.ini_options] table) will be considered as the configuration file and define the rootdir.

• #11978: Add --log-file-mode option to the logging plugin, enabling appending to log-files. This option accepts either "w" or "a" and defaults to "w".

  Previously, the mode was hard-coded to be "w" which truncates the file before logging.

... (truncated)

Commits

• 81653ee Adjust changelog manually for 8.1.1
• e60b4b9 Prepare release version 8.1.1
• 15fbe57 [8.1.x] Revert legacy path removals (#12093)
• 86c3aab [8.1.x] Do not import duplicated modules with --importmode=importlib (#12077)
• 5b82b0c [8.1.x] Yank version 8.1.0 (#12076)
• 0a53681 Merge pull request #12054 from pytest-dev/release-8.1.0
• b9a167f Prepare release version 8.1.0
• 00043f7 Merge pull request #12038 from bluetech/fixtures-rm-arg2index
• f4e1025 Merge pull request #12048 from bluetech/fixture-teardown-excgroup
• 43492f5 Merge pull request #12051 from jakkdl/test_debugging_pythonbreakpoint
• Additional commits viewable in compare view

Updates pytest-asyncio from 0.21.0 to 0.23.5.post1

Release notes

Sourced from pytest-asyncio's releases.

pytest-asyncio 0.23.5.post1

0.23.5 (2024-02-09)

• Declare compatibility with pytest 8 #737
• Fix typing errors with recent versions of mypy #769
• Prevent DeprecationWarning about internal use of asyncio.get_event_loop() from affecting test cases #757

Known issues

As of v0.23, pytest-asyncio attaches an asyncio event loop to each item of the test suite (i.e. session, packages, modules, classes, functions) and allows tests to be run in those loops when marked accordingly. Pytest-asyncio currently assumes that async fixture scope is correlated with the new event loop scope. This prevents fixtures from being evaluated independently from the event loop scope and breaks some existing test suites (see #706). For example, a test suite may require all fixtures and tests to run in the same event loop, but have async fixtures that are set up and torn down for each module. If you're affected by this issue, please continue using the v0.21 release, until it is resolved.

pytest-asyncio 0.23.5

0.23.5 (2024-02-09)

• Declare compatibility with pytest 8 #737
• Fix typing errors with recent versions of mypy #769
• Prevent DeprecationWarning about internal use of asyncio.get_event_loop() from affecting test cases #757

Known issues

As of v0.23, pytest-asyncio attaches an asyncio event loop to each item of the test suite (i.e. session, packages, modules, classes, functions) and allows tests to be run in those loops when marked accordingly. Pytest-asyncio currently assumes that async fixture scope is correlated with the new event loop scope. This prevents fixtures from being evaluated independently from the event loop scope and breaks some existing test suites (see #706). For example, a test suite may require all fixtures and tests to run in the same event loop, but have async fixtures that are set up and torn down for each module. If you're affected by this issue, please continue using the v0.21 release, until it is resolved.

pytest-asyncio 0.23.5a0

0.23.5 (UNRELEASED)

• Declare compatibility with pytest 8 #737
• Fix typing errors with recent versions of mypy #769

Known issues

As of v0.23, pytest-asyncio attaches an asyncio event loop to each item of the test suite (i.e. session, packages, modules, classes, functions) and allows tests to be run in those loops when marked accordingly. Pytest-asyncio currently assumes that async fixture scope is correlated with the new event loop scope. This prevents fixtures from being evaluated independently from the event loop scope and breaks some existing test suites (see #706). For example, a test suite may require all fixtures and tests to run in the same event loop, but have async fixtures that are set up and torn down for each module. If you're affected by this issue, please continue using the v0.21 release, until it is resolved.

pytest-asyncio 0.23.4

0.23.4 (2024-01-28)

• pytest-asyncio no longer imports additional, unrelated packages during test collection #729
• Addresses further issues that caused an internal pytest error during test collection
• Declares incompatibility with pytest 8 #737

pytest-asyncio 0.23.4a2

0.23.4 (UNRELEASED)

• pytest-asyncio no longer imports additional, unrelated packages during test collection #729
• Addresses further issues that caused an internal pytest error during test collection

Known issues

As of v0.23, pytest-asyncio attaches an asyncio event loop to each item of the test suite (i.e. session, packages, modules, classes, functions) and allows tests to be run in those loops when marked accordingly. Pytest-asyncio currently assumes that async fixture scope is correlated with the new event loop scope. This prevents fixtures from being evaluated independently from the event loop scope and breaks some existing test suites (see #706). For example, a test suite may require all fixtures and tests to run in the same event loop, but have async fixtures that are set up and torn down for each module. If you're affected by this issue, please continue using the v0.21 release, until it is resolved.

pytest-asyncio 0.23.4a1

0.23.4 (UNRELEASED)

• pytest-asyncio no longer imports additional, unrelated packages during test collection #729

Known issues

As of v0.23, pytest-asyncio attaches an asyncio event loop to each item of the test suite (i.e. session, packages, modules, classes, functions) and allows tests to be run in those loops when marked accordingly. Pytest-asyncio currently assumes that async fixture scope is correlated with the new event loop scope. This prevents fixtures from being evaluated independently from the event loop scope and breaks some existing test suites (see #706). For example, a test suite may require all fixtures and tests to run in the same event loop, but have async fixtures that are set up and torn down for each module. If you're affected by this issue, please continue using the v0.21 release, until it is resolved.

pytest-asyncio 0.23.4a0

... (truncated)

Commits

• b22d84e [docs] Fixes the example showing how to run all tests in a session-scoped loop.
• f1de446 Build(deps): Bump hypothesis in /dependencies/default
• b60649a Build(deps): Bump urllib3 from 2.2.0 to 2.2.1 in /dependencies/docs
• 4baec47 Build(deps): Bump typing-extensions in /dependencies/default
• d44e3ac Build(deps): Bump pytest from 8.0.0 to 8.0.2 in /dependencies/default
• cefa62e Build(deps): Bump coverage from 7.4.1 to 7.4.3 in /dependencies/default
• 2908860 Build(deps): Bump hypothesis in /dependencies/default
• 20bd7d8 Build(deps): Bump pypa/gh-action-pypi-publish from 1.8.11 to 1.8.12
• 3aef605 [build] Update actions/upload-artifact and actions/download-artifact to v4.
• 4b1908d [fix] Prevent DeprecationWarning from bubbling to user code.
• Additional commits viewable in compare view

Updates pylint from 3.0.2 to 3.1.0

Commits

• 053c2c3 Bump pylint to 3.1.0, update changelog
• c954636 Upgrade release documentation, and contributors.txt
• 7300ed2 Discover .pyi files (#9241)
• 9dbf3df Merge maintenance 3.0.x into main following 3.0.4 release (#9459)
• 28e89b0 Remove changelog fragments pertaining to 3.0.4
• 4332ea1 Merge branch 'maintenance/3.0.x' into main following 3.0.4 release
• 8115381 Bump pylint to 3.0.4, update changelog (#9458)
• 4bf3524 [false-negative] Fix for consider-using-min/max-builtin (#9127)
• 8c24b1e [pre-commit.ci] pre-commit autoupdate (#9448)
• f499686 Update astroid version to 3.1.0 (#9457)
• Additional commits viewable in compare view

Updates mypy from 1.6.0 to 1.9.0

Changelog

Sourced from mypy's changelog.

Mypy Release Notes

Mypy 1.9

We’ve just uploaded mypy 1.9 to the Python Package Index (PyPI). Mypy is a static type checker for Python. This release includes new features, performance improvements and bug fixes. You can install it as follows:

python3 -m pip install -U mypy

You can read the full documentation for this release on Read the Docs.

Breaking Changes

Because the version of typeshed we use in mypy 1.9 doesn't support 3.7, neither does mypy 1.9. (Jared Hance, PR 16883)

We are planning to enable local partial types (enabled via the --local-partial-types flag) later this year by default. This change was announced years ago, but now it's finally happening. This is a major backward-incompatible change, so we'll probably include it as part of the upcoming mypy 2.0 release. This makes daemon and non-daemon mypy runs have the same behavior by default.

Local partial types can also be enabled in the mypy config file:

local_partial_types = True

We are looking at providing a tool to make it easier to migrate projects to use --local-partial-types, but it's not yet clear whether this is practical. The migration usually involves adding some explicit type annotations to module-level and class-level variables.

Basic Support for Type Parameter Defaults (PEP 696)

This release contains new experimental support for type parameter defaults (PEP 696). Please try it out! This feature was contributed by Marc Mueller.

Since this feature will be officially introduced in the next Python feature release (3.13), you will need to import TypeVar, ParamSpec or TypeVarTuple from typing_extensions to use defaults for now.

This example adapted from the PEP defines a default for BotT:

from typing import Generic
from typing_extensions import TypeVar
class Bot: ...
BotT = TypeVar("BotT", bound=Bot, default=Bot)
</tr></table>

... (truncated)

Commits

• 5ff46f8 Remove +dev.
• 155909a [Release 1.9] Unsupport targetting 3.7. (#16883) (#16900)
• 6615cab [Release 1.9] Stubtest: ignore a new protocol dunder (#16895) (#16899)
• b956e6a stubtest: Private parameters can be omitted (#16507)
• ede0b20 Bump ruff to 0.2.0 (#16870)
• 7bdd61f stubgen: Fix crash on star unpack of TypeVarTuple (#16869)
• 8c2ef9d Update hashes in sync-typeshed.py following recent typeshed sync
• 0dd4b6f Revert use of ParamSpec for functools.wraps
• dd12a2d Revert typeshed ctypes change
• d132999 Revert sum literal integer change (#13961)
• Additional commits viewable in compare view

Updates types-pyyaml from 6.0.12.12 to 6.0.12.20240311

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 92.97%. Comparing base (26900cc) to head (0137d0e).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #108   +/-   ##
=======================================
  Coverage   92.97%   92.97%           
=======================================
  Files           7        7           
  Lines         541      541           
=======================================
  Hits          503      503           
  Misses         38       38           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[dependabot]

Superseded by #113.