-
Notifications
You must be signed in to change notification settings - Fork 4k
MINOR: [Doc][CI] Fix doctests failing on pandas 3 string types examples #49088
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
060eab3 to
f14ade1
Compare
|
|
||
| >>> print(dict_array.type) | ||
| dictionary<values=string, indices=int64, ordered=0> | ||
| dictionary<values=...string, indices=int64, ordered=0> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This one should not be needed? (the dictionary here is created just through pyarrow, no pandas involved?)
| 7 baz | ||
| dtype: category | ||
| Categories (3, object): ['foo', 'bar', 'baz'] | ||
| Categories (3, ...): ['foo', 'bar', 'baz'] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
FWIW, I think if we know the doctests will run on an instance with pandas>=3, I would just update those to use pandas 3 output, because that will be less confusing for people reading the docs ("what do those 3 dots mean here?").
| Categories (3, ...): ['foo', 'bar', 'baz'] | |
| Categories (3, str): ['foo', 'bar', 'baz'] |
| >>> schema | ||
| f0: int64 | ||
| f1: string | ||
| f1: ...string |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also here, is this actually needed? The example here is pure pyarrow, and that should always be using pyarrow's default of "string" ?
See #48619 (comment)
Rationale for this change
Fix CI failures
What changes are included in this PR?
Tests are made more general to allow for Pandas 2 and Pandas 3 style string types
Are these changes tested?
By CI
Are there any user-facing changes?
No