typing: improve type coverage in sqlalchemy.sql.compiler for issue #6810 #12766
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hi @CaselIT, I’ve raised this PR to improve the typing coverage of the Thanks! |
KapilDagur
force-pushed
the
typing/sqlalchmey-sql-compiler
branch
from
0318c81 to
c72fd65
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
✅ typing: improve type coverage in
sqlalchemy.sql.compilerfor issue #6810Overview
This pull request enhances the type coverage of the
sqlalchemy.sql.compilermodule as part of the gradual migration toward complete static typing under--strictmode (#6810).The typing improvements were made with careful consideration of:
Mypy
--strictcompatibilityRuntime behavior preservation
Avoidance of external API typing regressions
Maintaining test and slot safety
Isolating downstream typing impact
✅ Validation Checklist