Repository navigation
Conversation
SQLAlchemy 2.1 types Result with variadic generics, so mypy 2.3.0 reports var-annotated on bare scalar_one() assignments.
SQLAlchemy 2.1 retyped Result and broke the type gate, so the next minor should be a deliberate bump. mypy stays pinned with data-pipeline.
This was referenced Oct 26, 2026
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
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.
What and why
SQLAlchemy 2.1 retyped
Resultand broke the type gate with no change in this repo. This capssqlalchemyat<2.2so the next minor release is a deliberate bump. 2.1 stays allowed because the suites pass on 2.1.6.mypy==2.3.0is unchanged, and data-pipeline now pins the same release.Depends on #102; this branch starts from it. Paired with Idea2Strategy/Idea2Strategy-data-pipeline#66.
Checklist