BUG: Fix inconsistent datetime types between calamine and openpyxl readers (#59186)#63318
Uh oh!
There was an error while loading. Please reload this page.
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
…aders (pandas-dev#59186) The calamine Excel reader was returning pd.Timestamp and pd.Timedelta for datetime values in mixed-type columns, while openpyxl returns standard library datetime.datetime and datetime.timedelta objects. This change modifies the calamine reader to return standard library datetime types, ensuring consistent behavior across Excel reader engines. - Return datetime.datetime as-is instead of converting to pd.Timestamp - Convert date objects to datetime to match openpyxl behavior - Return datetime.timedelta as-is instead of converting to pd.Timedelta - Remove unused pandas import - Update test helper get_exp_unit() to reflect new consistent behavior
mroeschke requested changes Dec 10, 2025
pandas/io/excel/_calamine.py Outdated
Comment on lines 115 to 118
| elifisinstance(value, timedelta): | ||
| returnpd.Timedelta(value) | ||
| # Return datetime.timedelta as-is to match openpyxl behavior (GH#59186) | ||
| # (previously returned pd.Timedelta) | ||
| returnvalue |
Member
There was a problem hiding this comment.
Can you combine this branch with the isinstance(value, datetime) branch by combining the isinstance checks?
mroeschke approved these changes Dec 11, 2025
mroeschke merged commit 447249a into pandas-dev:main 41 checks passed
Uh oh!
There was an error while loading. Please reload this page.
Member
mroeschke commented Dec 11, 2025
Thanks @yjennyli |
Sign up for freeto 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.
closes#59186
When reading Excel files with mixed data types (strings, dates, numbers in the same column), the calamine and openpyxl engines returned different Python types for datetime values:
datetime.datetimepd.TimestampThis is confusing for users who expect consistent behavior regardless of which engine they use.
This PR Changes the calamine reader to return standard library types (
datetime.datetime,datetime.timedelta) instead of pandas types (pd.Timestamp,pd.Timedelta), matching openpyxl's behavior.Testing:
All existing Excel reader tests pass (1467 passed)
Manual testing confirms both engines now return the same types