DOC: Clarify allowed values for on_bad_lines in read_csv #58662
Merged
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.
Move the callable options out of the version added/changed tags and improve the flow.
[ ] closes #xxxx (Replace xxxx with the GitHub issue number)[ ] Tests added and passed if fixing a bug or adding a new feature[ ] Added type annotations to new arguments/methods/functions.[ ] Added an entry in the latestdoc/source/whatsnew/vX.X.X.rst
file if fixing a bug or adding a new feature.Check my work to make sure I got the details right, please. One thing is, I'm not sure if "process" is the right term for the PyArrow
invalid_row_handler
since all it does is say "skip" or "error".BTW,
invalid_row_handler
isn't mentioned specifically, so at first I thought "signature as described in pyarrow documentation" was referring to the signature of theParseOptions
constructor.Also, the description should probably state explicitly what happens when the function returns a list of strings with the right number of elements (with
engine='python'
). I haven't used it myself, but I'm inferring it gets forwarded to the parser that turns a table of strings into a dataframe.