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

Update read_table #362

Merged
merged 4 commits into from
Jun 11, 2019
Merged

Update read_table #362

merged 4 commits into from
Jun 11, 2019

Conversation

adnanhemani
Copy link
Member

@adnanhemani adnanhemani commented Jun 11, 2019

[X] Wrote test for feature
[N/A] Added changes in the Changelog section in README.md
[N/A] Bumped version number (delete if unneeded)

Changes proposed:
Used the solution in #353 and added more robust testing. Thank you @deculler!

@adnanhemani
Copy link
Member Author

So far this looks like there's actually no problems - @davidwagner if you could please test against more dense/heavier data files, that'd be great! I have a sinking feeling that something's off here, but I can't tell what and it works 100% (at least locally). Maybe I'm just being paranoid.

@davidwagner
Copy link
Member

I tested on a few csv files I have lying around, including the large one used in my privacy lecture and some ones that trigger Unicode errors, and the behavior before vs after was identical in all cases. So this seems fine as far as all my testing indicates.

@davidwagner davidwagner merged commit b59803c into master Jun 11, 2019
@davidwagner davidwagner deleted the updae_read_table branch June 11, 2019 06:17
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.

2 participants