BUG: Fix inconsistent datetime types between calamine and openpyxl readers (#59186) #63318
+6
−10
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