Fix mypy type errors in Neo4j provider for SQLAlchemy 2 upgrade #56785
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
RoyLee1224
force-pushed
the
fix/providers-neo4j-mypy
branch
2 times, most recently
from
ec63c37 to
02579f1
Compare
potiuk
reviewed
Oct 18, 2025
RoyLee1224
force-pushed
the
fix/providers-neo4j-mypy
branch
from
6405dbe to
5fab1b5
Compare
nailo2c
pushed a commit
to nailo2c/airflow
that referenced
this pull request
Oct 20, 2025
…he#56785) * fix: Fix mypy type errors in Neo4j provider for SQLAlchemy 2 upgrade * fix: Add backward-compatible import for timezone * fix: Replace direct timezone import with lazy_compat in Neo4j provider
TyrellHaywood
pushed a commit
to TyrellHaywood/airflow
that referenced
this pull request
Oct 22, 2025
…he#56785) * fix: Fix mypy type errors in Neo4j provider for SQLAlchemy 2 upgrade * fix: Add backward-compatible import for timezone * fix: Replace direct timezone import with lazy_compat in Neo4j provider
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Related issue
part of #56738
Changes
airflow.utilstolazy_compatfor Airflow 3.1+ compatibilityTest
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.