ENH: Make pd.to_datetime with format parameter more robust to dirty data (#62840) #63171
+1,048
−72
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.
This PR adds a new
thresholdargument toto_datetimethat allows users to specify the minimum fraction of valid datetime components required for parsing to succeed. For this feature, "successful" parsing means that the function returns either a validTimestamporNaT(i.e., it does not raise an exception). The threshold determines whether partially-invalid values produceNaTor raise an error. This enables more flexible and robust parsing behavior for partially-invalid dates while preserving strict behavior by default (threshold=1.0).Summary of changes
thresholdargument toto_datetime.[0.0, 1.0].