fix: add pandas 3.0 compatibility by disabling strict string dtype #980
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
Pandas 3.0 uses strict string dtype by default, which raises TypeError when assigning non-string values (int, tuple, etc.) to string columns. This breaks many places in the codebase that rely on the old permissive object dtype behavior. Setting `pd.options.future.infer_string = False` globally restores the pandas 2.x behavior where string columns use object dtype. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
ElpadoCan
approved these changes
Jan 23, 2026
Collaborator
|
Thank you @keejkrej, I didn't try pandas 3.0 yet, so thanks for doing that! |
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.0 uses strict string dtype by default, which raises TypeError when assigning non-string values (int, tuple, etc.) to string columns. This breaks many places in the codebase that rely on the old permissive object dtype behavior.
Setting
pd.options.future.infer_string = Falseglobally restores the pandas 2.x behavior where string columns use object dtype.