-
Notifications
You must be signed in to change notification settings - Fork 166
feat: add separator
argument in read_csv
/scan_csv
#2989
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
raisadz
wants to merge
19
commits into
narwhals-dev:main
Choose a base branch
from
raisadz:feat/add-separator-arg
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
19 commits
Select commit
Hold shift + click to select a range
409dd4b
feat: add `separator` argument to `read_csv` / `scan_csv`
raisadz 8143ae3
Merge remote-tracking branch 'upstream/main' into feat/add-separator-arg
raisadz 9d6e850
add stable api
raisadz 9000f88
Merge remote-tracking branch 'upstream/main' into feat/add-separator-arg
raisadz b99dfcd
add coverage
raisadz 6b90890
Merge remote-tracking branch 'upstream/main' into feat/add-separator-arg
raisadz c4ff1c6
add session for sqlframe for coverage
raisadz 00f0bc2
Update narwhals/functions.py
raisadz af21d2f
add separator validation
raisadz 59a5b6b
Merge remote-tracking branch 'upstream/main' into feat/add-separator-arg
raisadz d0c7283
fix merge
raisadz ff68327
modify kwargs for pyarrow
raisadz b7cb02c
restore header that was there before
raisadz 7cfae8f
Merge remote-tracking branch 'upstream/main' into feat/add-separator-arg
raisadz 126c5c4
Update narwhals/functions.py
raisadz cf7c67d
Merge remote-tracking branch 'origin/feat/add-separator-arg' into feaβ¦
raisadz 8ace0f9
Merge remote-tracking branch 'upstream/main' into feat/add-separator-arg
raisadz 512c529
make `validate` support functions private
raisadz ec12904
Merge remote-tracking branch 'upstream/main' into feat/add-separator-arg
raisadz File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nevermind I completely misread this
Fake panic review
The issue I have with this is that if any other argument was provided in
parse_options
then it will be silently ignored.Say someone is calling the following:
Then at the end of
validate_separator_pyarrow
, we will end up withcsv.ParseOptions(delimiter=separator, ignore_empty_lines=True)
(i.e. the default value), silently.I agree that hardcoding fields as suggested in #2989 (review) is not ideal, yet pyarrow does not provide much else we can use. We could dynamically lookup its
__dir__
or useinspect.get_members
, exclude dunder methods, but for example we would end up withvalidate
andequals
, which are not attribute to set at instantiation.Unsuccessful tentatives I tried:
inspect.signature
dataclasses.fields
From the stubs I got tricked into thinking that is a dataclass:
I have mixed feelings as now a pyarrow user should pass both
separator=xyz, parse_options=csv.ParseOptions(delimiter=xyz)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @FBruzzesi!
A user won't need to pass both
separator
anddelimiter
asif "parse_options" not in kwargs:
then wereturn {"parse_options": csv.ParseOptions(delimiter=separator)}
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
right, so someone would only need to pass both
separator
anddelimiter
if they were specifying another parse option (likedouble_quote
)tbh I think this is fine
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since our default is:
and matches
pyarrow
's default:Alternative
ParseOptions.delimiter
has higher precedence unlessseparator
overrides the default.In either case - every other argument is respected
Show definitions
Would this behavior not be more ideal?
Although it is
cython
, the important part is they're all properties with settershttps://github.com/apache/arrow/blob/f8b20f131a072ef423e81b8a676f42a82255f4ec/python/pyarrow/_csv.pyx#L435-L543
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hmmm yes, that does sound better actually, thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks Marco
with (#2989 (comment)) in mind ...
Not sure if this is on
duckdb
orsqlframe
, butsep
has higher precedence thandelim
Personally, I think we're best off just defining rule(s) and documenting what we do for each backend if needed.
So instead of
We either:
If any backend raises on non-matching arguments - I say let them - as it saves us the hassle π