Fix encoding and fill in Write In column for WI results #275
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This addresses two things:
Wisconsin has some candidate names that include non-latin characters (Juan Colás for example). The ideal way to handle it seemed to be opening the file in binary and then reading the CSV contents using UTF-8.
For Wisconsin results, write-in candidates have
(Write-In)in the candidate name. Now when baking results, that will be removed from the candidate name and thewrite-incolumn will be filled in based on whether that occurred. See issue: Wisconsin results files don't have total votes/winner/write-in columns filled in #274