Update sqlalchemy requirement from ~=1.4.22 to ~=1.4.36
Created by: dependabot[bot]
Updates the requirements on sqlalchemy to permit the latest version.
Release notes
Sourced from sqlalchemy's releases.
1.4.36
Released: April 26, 2022
orm
[orm] [bug] [regression] Fixed regression where the change made for #7861, released in version 1.4.33, that brought the
Insert
construct to be partially recognized as an ORM-enabled statement did not properly transfer the correct mapper / mapped table state to theSession
, causing theSession.get_bind()
method to fail for aSession
that was bound to engines and/or connections using theSession.binds
parameter.References: #7936
orm declarative
[orm] [declarative] [bug] Modified the
DeclarativeMeta
metaclass to passcls.__dict__
into the declarative scanning process to look for attributes, rather than the separate dictionary passed to the type's__init__()
method. This allows user-defined base classes that add attributes within an__init_subclass__()
to work as expected, as__init_subclass__()
can only affect thecls.__dict__
itself and not the other dictionary. This is technically a regression from 1.3 where__dict__
was being used.References: #7900
engine
[engine] [bug] Fixed a memory leak in the C extensions which could occur when calling upon named members of
Row
when the member does not exist under Python 3; in particular this could occur during NumPy transformations when it attempts to call members such as.__array__
, but the issue was surrounding anyAttributeError
thrown by theRow
object. This issue does not apply to version 2.0 which has already transitioned to Cython. Thanks much to Sebastian Berg for identifying the problem.References: #7875
[engine] [bug] Added a warning regarding a bug which exists in the
Result.columns()
method when passing 0 for the index in conjunction with aResult
that will return a single ORM entity, which indicates that the current behavior ofResult.columns()
is broken in this case as theResult
object will yield scalar values and notRow
objects. The issue will be fixed in 2.0, which would be a backwards-incompatible change for code that relies on the current broken
... (truncated)
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 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)