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.

Sign up for GitHub

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

Jump to bottom

column types no longer being correctly parsed #42

Open
tbeason opened this issue Feb 21, 2022 · 1 comment
Open

column types no longer being correctly parsed #42

tbeason opened this issue Feb 21, 2022 · 1 comment
Labels
bug Something isn't working

Comments

@tbeason
Copy link
Owner

tbeason commented Feb 21, 2022

😞 a recent change to CSV or Parsers has broken the parsing here. Numbers are being represented by strings...

As a workaround before I get it fixed, you can do parse(Float64,x) or parse(Union{Float64,Missing},x) on elements (or broadcast to entire columns).
@tbeason tbeason added the bug Something isn't working label Feb 21, 2022
@tbeason
Copy link
Owner Author

tbeason commented Feb 25, 2022

I can no longer reproduce this... not sure what was going on. I'll leave it open for a bit in case I notice it again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@tbeason