[v3-3-test] Add support for pandas 3 based xcoms in airflow (#71103) - #71169
Merged
Conversation
boring-cyborg
Bot
added
area:providers
area:task-sdk
provider:amazon
vatsrahul1001
added
the
type:misc/internal
1 task
amoghrajesh
changed the title
vatsrahul1001
added a commit
that referenced
this pull request
Aug 5, 2026
Backport of #71100, which reverted "Limit pandas to < 3 for DataFrame XComs" (#70791) on main. v3-3-test carried the cap via the #70912 backport; reverting that commit removes the cap here too so the release branch matches main. The pandas-3 XCom serializer support lands separately in #71169 (the #71103 backport) -- the same order main used (#71100 before #71103). uv.lock regenerated with uv 0.12.1 to drop the pandas <3 specifier.
* Keep DataFrame XComs working on pandas 3 pandas 3 exposes its public classes from the `pandas` namespace, so a DataFrame is now qualified as `pandas.DataFrame` rather than `pandas.core.frame.DataFrame`. The serializer was registered only under the old name, so pushing a DataFrame through XCom raised "cannot serialize object of type <class 'pandas.DataFrame'>". Both names are registered so values written by either version stay readable. pandas 3 also infers a str column where it used to infer object, and keeps its missing values as NA instead of stringifying them, which the amazon and salesforce tests asserted on. * Document pandas 3 impact on DataFrame XComs Deployments need to know that every component has to carry the pandas 3 support before pandas 3 reaches any worker, that a rollback strands the XComs written in the meantime, and that a pulled DataFrame now takes its dtypes from the reader's pandas version. * Name the pandas 3 newsfragment after its own pull request * Add regression test for the pandas 2/3 cross-version registry lookup * rename newsfragment file --------- Co-authored-by: Jarek Potiuk <jarek@potiuk.com> (cherry picked from commit 4091ccf)
vatsrahul1001
force-pushed
the
backport-4091ccf-v3-3-test
branch
from
August 5, 2026 15:54
6c9832f to
f1ab6ec
Compare
vatsrahul1001
added a commit
that referenced
this pull request
Aug 5, 2026
Backport of #71100, which reverted "Limit pandas to < 3 for DataFrame XComs" (#70791) on main. v3-3-test carried the cap via the #70912 backport; reverting that commit removes the cap here too so the release branch matches main. The pandas-3 XCom serializer support lands separately in #71169 (the #71103 backport) -- the same order main used (#71100 before #71103). uv.lock regenerated with uv 0.12.1 to drop the pandas <3 specifier.
vatsrahul1001
pushed a commit
that referenced
this pull request
Aug 5, 2026
* Keep DataFrame XComs working on pandas 3 pandas 3 exposes its public classes from the `pandas` namespace, so a DataFrame is now qualified as `pandas.DataFrame` rather than `pandas.core.frame.DataFrame`. The serializer was registered only under the old name, so pushing a DataFrame through XCom raised "cannot serialize object of type <class 'pandas.DataFrame'>". Both names are registered so values written by either version stay readable. pandas 3 also infers a str column where it used to infer object, and keeps its missing values as NA instead of stringifying them, which the amazon and salesforce tests asserted on. * Document pandas 3 impact on DataFrame XComs Deployments need to know that every component has to carry the pandas 3 support before pandas 3 reaches any worker, that a rollback strands the XComs written in the meantime, and that a pulled DataFrame now takes its dtypes from the reader's pandas version. * Name the pandas 3 newsfragment after its own pull request * Add regression test for the pandas 2/3 cross-version registry lookup * rename newsfragment file --------- (cherry picked from commit 4091ccf) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
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
2 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.
pandas 3 exposes its public classes from the
pandasnamespace, so a DataFrame is now qualified aspandas.DataFramerather thanpandas.core.frame.DataFrame. The serializer was registered only under the old name, so pushing a DataFrame through XCom raised "cannot serialize object of type <class 'pandas.DataFrame'>". Both names are registered so values written by either version stay readable.pandas 3 also infers a str column where it used to infer object, and keeps its missing values as NA instead of stringifying them, which the amazon and salesforce tests asserted on.
Deployments need to know that every component has to carry the pandas 3 support before pandas 3 reaches any worker, that a rollback strands the XComs written in the meantime, and that a pulled DataFrame now takes its dtypes from the reader's pandas version.
Name the pandas 3 newsfragment after its own pull request
Add regression test for the pandas 2/3 cross-version registry lookup
rename newsfragment file
(cherry picked from commit 4091ccf)
Was generative AI tooling used to co-author this PR?
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.