fix: coerce nanoseconds (#3357) - #3407
Open
wasim-builds wants to merge 1 commit into
Open
Conversation
wasim-builds
force-pushed
the
fix/issue-3357-coerce-nanoseconds
branch
from
July 23, 2026 14:59
0211f18 to
8c440d5
Compare
Author
|
Rebased onto latest |
wasim-builds
changed the title
Author
|
Hey 👋 Friendly bump on this one — small fix for nanosecond coercion (Fixes #3357). No rush, just checking in! 🙏 |
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
1 participant
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.
Fixes #3357
Problem
DataFrame columns with nanosecond-resolution datetime values are not handled correctly during type coercion.
Fix
Add nanosecond coercion logic in
awswrangler/_data_types.py.Scope
Single-file change in
awswrangler/_data_types.py.Verification
Datetime columns with nanosecond precision are correctly coerced without precision loss or overflow errors.