-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Complement type annotations for ARRAY #12386
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
This will help when adding type annotations to ARRAY next.
I was also thinking about making |
makes sense doing that in a follow up pr |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK, this is sqla-tester setting up my work on behalf of CaselIT to try to get revision c9513ce of this pull request into gerrit so we can run tests and reviews and stuff
New Gerrit review created for change c9513ce: https://gerrit.sqlalchemy.org/c/sqlalchemy/sqlalchemy/+/5763 |
Gerrit review https://gerrit.sqlalchemy.org/c/sqlalchemy/sqlalchemy/+/5763 has been merged. Congratulations! :) |
Gerrit review https://gerrit.sqlalchemy.org/c/sqlalchemy/sqlalchemy/+/5783 has been merged. Congratulations! :) |
This complements the type annotations of the `ARRAY` class, in preparation of #12384. This pull request is: - [ ] A documentation / typographical / small typing error fix - Good to go, no issue or tests are needed - [ ] A short code fix - please include the issue number, and create an issue if none exists, which must include a complete example of the issue. one line code fixes without an issue and demonstration will not be accepted. - Please include: `Fixes: #<issue number>` in the commit message - please include tests. one line code fixes without tests will not be accepted. - [x] A new feature implementation - please include the issue number, and create an issue if none exists, which must include a complete example of how the feature would look. - Please include: `Fixes: #<issue number>` in the commit message - please include tests. Related to #6810 Closes: #12386 Pull-request: #12386 Pull-request-sha: c9513ce Change-Id: If9df4708c8e597eedc79ee3990792fa6c72f1afe (cherry picked from commit 0bf7e02)
Now `Column(type_=ARRAY(Integer)` is inferred as `Column[Sequence[int]]` instead as `Column[Sequence[Any]]` previously. This only works with the `type_` argument to Column, but that's not new. This follows from a suggestion at sqlalchemy#12386 (comment). Related to sqlalchemy#6810.
Now `Column(type_=ARRAY(Integer)` is inferred as `Column[Sequence[int]]` instead as `Column[Sequence[Any]]` previously. This only works with the `type_` argument to Column, but that's not new. This follows from a suggestion at sqlalchemy#12386 (comment). Related to sqlalchemy#6810.
Now `Column(type_=ARRAY(Integer)` is inferred as `Column[Sequence[int]]` instead as `Column[Sequence[Any]]` previously. This only works with the `type_` argument to Column, but that's not new. This follows from a suggestion at #12386 (comment). Related to #6810. Closes: #12443 Pull-request: #12443 Pull-request-sha: 2fff4e8 Change-Id: I87b828fd82d10fbf157141db3c31f0ec8149caad (cherry picked from commit 500adfa)
Now `Column(type_=ARRAY(Integer)` is inferred as `Column[Sequence[int]]` instead as `Column[Sequence[Any]]` previously. This only works with the `type_` argument to Column, but that's not new. This follows from a suggestion at #12386 (comment). Related to #6810. Closes: #12443 Pull-request: #12443 Pull-request-sha: 2fff4e8 Change-Id: I87b828fd82d10fbf157141db3c31f0ec8149caad
Description
This complements the type annotations of the
ARRAY
class, in preparation of #12384.Checklist
This pull request is:
must include a complete example of the issue. one line code fixes without an
issue and demonstration will not be accepted.
Fixes: #<issue number>
in the commit messageinclude a complete example of how the feature would look.
Fixes: #<issue number>
in the commit messageRelated to #6810