[MINOR][PYTHON] Fix try_to_date docstring typo#56618
Open
mh0w wants to merge 2 commits into
Open
Conversation
Fix a docstring typo in pyspark.sql.functions.try_to_date. Current text says “special version of try_to_date”, which is self-referential. Correct text is “special version of to_date”. See, for reference, the other try_ functions.
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.
What changes were proposed in this pull request?
This PR fixes a docstring typo in
pyspark.sql.functions.try_to_date.The current docstring says that
try_to_dateis a special version oftry_to_date, which is self-referential. It should say thattry_to_dateis a special version ofto_date, matching the actual relationship and the wording used by similartry_functions.Why are the changes needed?
The current wording appears to be a typo.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Not applicable. This PR only corrects a docstring typo.
Was this patch authored or co-authored using generative AI tooling?
No.