-
Notifications
You must be signed in to change notification settings - Fork 140
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
CSV.File is corrupting missingstrings parameter #780
Comments
Am386DX-40
pushed a commit
to Am386DX-40/CSV.jl
that referenced
this issue
Nov 19, 2020
Closed
quinnj
added a commit
to JuliaData/Parsers.jl
that referenced
this issue
Nov 20, 2020
Fixes JuliaData/CSV.jl#780. The issue here is Parsers.Options was assuming ownership of and modifying the input `sentinel` if it was a `Vector{String}`. The fix is to make a copy instead and then we can modify and use it to store references to other strings as needed.
quinnj
added a commit
to JuliaData/Parsers.jl
that referenced
this issue
Nov 20, 2020
Fixes JuliaData/CSV.jl#780. The issue here is Parsers.Options was assuming ownership of and modifying the input `sentinel` if it was a `Vector{String}`. The fix is to make a copy instead and then we can modify and use it to store references to other strings as needed.
Thanks for the report. This is actually a Parsers.jl issue, which is modifying the input missingstrings array. Fix is up there: JuliaData/Parsers.jl#73. |
quinnj
added a commit
to JuliaData/Parsers.jl
that referenced
this issue
Nov 20, 2020
Fixes JuliaData/CSV.jl#780. The issue here is Parsers.Options was assuming ownership of and modifying the input `sentinel` if it was a `Vector{String}`. The fix is to make a copy instead and then we can modify and use it to store references to other strings as needed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
shows:
I would expect it to stay:
The text was updated successfully, but these errors were encountered: