Skip to content

Bump sqlalchemy from 1.4.27 to 1.4.28 in /requirements

Guillaume Gay requested to merge dependabot/pip/requirements/sqlalchemy-1.4.28 into main

Created by: dependabot[bot]

Bumps sqlalchemy from 1.4.27 to 1.4.28.

Release notes

Sourced from sqlalchemy's releases.

1.4.28

Released: December 9, 2021

platform

  • [platform] [bug] Python 3.10 has deprecated "distutils" in favor of explicit use of "setuptools" in PEP 632; SQLAlchemy's setup.py has replaced imports accordingly. However, since setuptools itself only recently added the replacement symbols mentioned in pep-632 as of November of 2021 in version 59.0.1, setup.py still has fallback imports to distutils, as SQLAlchemy 1.4 does not have a hard setuptools versioning requirement at this time. SQLAlchemy 2.0 is expected to use a full PEP 517 installation layout which will indicate appropriate setuptools versioning up front.

    References: #7311

orm

  • [orm] [bug] [ext] Fixed issue where the internal cloning used by the _orm.PropComparator.any() method on a _orm.relationship() in the case where the related class also makes use of ORM polymorphic loading, would fail if a hybrid property on the related, polymorphic class were used within the criteria for the any() operation.

    References: #7425

  • [orm] [bug] [mypy] Fixed issue where the _orm.as_declarative() decorator and similar functions used to generate the declarative base class would not copy the __class_getitem__() method from a given superclass, which prevented the use of pep-484 generics in conjunction with the Base class. Pull request courtesy Kai Mueller.

    References: #7368

  • [orm] [bug] [regression] Fixed ORM regression where the new behavior of "eager loaders run on unexpire" added in #1763 would lead to loader option errors being raised inappropriately for the case where a single _orm.Query or _sql.Select were used to load multiple kinds of entities, along with loader options that apply to just one of those kinds of entity like a _orm.joinedload(), and later the objects would be refreshed from expiration, where the loader options would attempt to be applied to the mismatched object type and then raise an exception. The check for this mismatch now bypasses raising an error for this case.

    References: #7318

  • [orm] [bug] User defined ORM options, such as those illustrated in the dogpile.caching

... (truncated)

Commits

Dependabot compatibility score

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 ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Merge request reports