diff options
| author | Mike Bayer <mike_mp@zzzcomputing.com> | 2023-01-19 15:34:46 -0500 |
|---|---|---|
| committer | Mike Bayer <mike_mp@zzzcomputing.com> | 2023-01-20 09:13:58 -0500 |
| commit | d1eeef5e67fa4632f88a894f0c5cf4445f04ba2b (patch) | |
| tree | 30f2ad05dbf45bb2aa5dc33502a24cbdc5281097 /lib/sqlalchemy/sql/coercions.py | |
| parent | e82a5f19e1606500ad4bf6a456c2558d74df24bf (diff) | |
| download | sqlalchemy-d1eeef5e67fa4632f88a894f0c5cf4445f04ba2b.tar.gz | |
typing updates
The :meth:`_sql.ColumnOperators.in_` and
:meth:`_sql.ColumnOperators.not_in_` are typed to include
``Iterable[Any]`` rather than ``Sequence[Any]`` for more flexibility in
argument type.
The :func:`_sql.or_` and :func:`_sql.and_` from a typing perspective
require the first argument to be present, however these functions still
accept zero arguments which will emit a deprecation warning at runtime.
Typing is also added to support sending the fixed literal ``False`` for
:func:`_sql.or_` and ``True`` for :func:`_sql.and_` as the first argument
only, however the documentation now indicates sending the
:func:`_sql.false` and :func:`_sql.true` constructs in these cases as a
more explicit approach.
Fixed typing issue where iterating over a :class:`_orm.Query` object
was not correctly typed.
Fixes: #9122
Fixes: #9123
Fixes: #9125
Change-Id: I500e3e1b826717b3dd49afa1e682c3c8279c9226
Diffstat (limited to 'lib/sqlalchemy/sql/coercions.py')
| -rw-r--r-- | lib/sqlalchemy/sql/coercions.py | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/lib/sqlalchemy/sql/coercions.py b/lib/sqlalchemy/sql/coercions.py index 9fe65b0cd..3b187e49d 100644 --- a/lib/sqlalchemy/sql/coercions.py +++ b/lib/sqlalchemy/sql/coercions.py @@ -311,7 +311,7 @@ def expect( @overload def expect( - role: Union[Type[roles.JoinTargetRole], Type[roles.OnClauseRole]], + role: Type[roles.JoinTargetRole], element: _JoinTargetProtocol, **kw: Any, ) -> _JoinTargetProtocol: |