Skip to content
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

Allow more permissive string parsing #973

Closed
wants to merge 4 commits into from

Conversation

nickrobinson251
Copy link
Collaborator

@nickrobinson251 nickrobinson251 commented Jan 29, 2022

I don't actually see why "Data from A.-M. Guerry, \"Essay on the Moral Statistics of France\"" is getting parsed only as Data from A.-M. Guerry, , but it is even with prior versions of CSV (e.g. v0.8) and Parsers (e.g. v1), so this PR just restores the behaviour we had with Parsers v2.2.0, but which broke when we started marking such cases as invalid in Parsers v2.2.1

cc @quinnj @andreasnoack

- Set the value if we have `valueok` rather
  than relying on `!invalid`, to avoid erroring
  when we have successfully parsed a string but
  then hit an invalid delimiter.
- Fixes JuliaData#972.
@nickrobinson251
Copy link
Collaborator Author

aaaand this changes breaks a bunch of other cases 😆

i will keep investigating for a better fix (or Jacob might immediately just see what's up)

@nickrobinson251
Copy link
Collaborator Author

maybe just not needed 😄
#972 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

CSV.File throws for MethodError for RDatasets csv file
1 participant