We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
The type hints for the AsyncSession.scalars() method uses the keyword argument parameters, but the actual argument is named params.
AsyncSession.scalars()
parameters
params
The same issue applies to AsyncSession.stream_scalars() and to the async_scoped_session proxies for these.
AsyncSession.stream_scalars()
async_scoped_session
See:
sqlalchemy2-stubs/sqlalchemy-stubs/ext/asyncio/session.pyi
Lines 135 to 146 in ccca179
Lines 211 to 222 in ccca179
The text was updated successfully, but these errors were encountered:
Thanks for reporting.
If you could provide a PR it would be great
Sorry, something went wrong.
AsyncSession: correct (stream_)scalars arg name (#238)
cf492ed
The execute parameters argument is named 'params', not 'parameters'. See the [`AsyncSession.scalars()`][1] and [`AsyncSession.stream_scalars()`][2] implementations. Fixes #230 [1]: https://github.com/sqlalchemy/sqlalchemy/blob/a84f474051cae710e33b3d9486194ed534fe0167/lib/sqlalchemy/ext/asyncio/session.py#L249-L256 [2]: https://github.com/sqlalchemy/sqlalchemy/blob/a84f474051cae710e33b3d9486194ed534fe0167/lib/sqlalchemy/ext/asyncio/session.py#L338-L345
Successfully merging a pull request may close this issue.
The type hints for the
AsyncSession.scalars()
method uses the keyword argumentparameters
, but the actual argument is namedparams
.The same issue applies to
AsyncSession.stream_scalars()
and to theasync_scoped_session
proxies for these.See:
sqlalchemy2-stubs/sqlalchemy-stubs/ext/asyncio/session.pyi
Lines 135 to 146 in ccca179
sqlalchemy2-stubs/sqlalchemy-stubs/ext/asyncio/session.pyi
Lines 211 to 222 in ccca179
The text was updated successfully, but these errors were encountered: