Fix mypy errors in otel_tracer related to dropping python 3.9 support #52170
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
|
@eladkal Can you please take a look? |
eladkal
approved these changes
Jun 24, 2025
github-actions bot
pushed a commit
that referenced
this pull request
Jun 24, 2025
(cherry picked from commit c6693cb) Co-authored-by: Christos Bisias <[email protected]>
Backport successfully created: v3-0-test
|
eladkal
pushed a commit
that referenced
this pull request
Jun 25, 2025
(cherry picked from commit c6693cb) Co-authored-by: Christos Bisias <[email protected]>
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.
This is related to #52072. Using python 3.10 makes the static checks stricter. With these changes there will be no mypy failures after python 3.9 support is dropped.
^ 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.