-
Notifications
You must be signed in to change notification settings - Fork 68
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
[SYNPY-1521] Fixes asDataFrame
kwarg
Collision Issue
#1132
Conversation
Hello @BWMac! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:
Comment last updated at 2024-09-24 21:00:21 UTC |
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.
LGTM! 🔥
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.
Logic looks good to me! Thanks, just 1 comment on how we could improve the docstring.
Problem:
In #1127, I added the ability to pass
pandas.read_csv
keyword arguments toCsvFileTable.asDataFrame
to give users the ability to have more control over the dataframe that was produced (such as determining which values should be treated as NA). An unintended side-effect of this was that users could unintentionally pass a keyword argument that is already set in the code that callsread_csv
in_csv_to_pandas_df
, causing an error like this one:Solution:
Add logic to
_csv_to_pandas_df
which creates a keyword arguments dictionary which is then updated to resolve any conflicts while giving precedence to the arguments passed intentionally by the user.Testing:
_csv_to_pandas_df
. Previously there were none.