Fix double quotation mark(") in each column for Pandas csv parser compatibility. #8
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 commit fixes some double quotation mark(") pair mismatch errors in each column, without compromising the meaning of the original sentence. (and fixes issue #2 , #4 , #5 , too.)
pandas.read_csv() method is often used for parsing tsv files in many projects, including huggingface datasets.
(e.g. https://huggingface.co/datasets/kor_nlu) but that method utilizes double quotation mark(") at the beginning to escape special characters in the column (same as csv convention), as a result, the TAB character is not parsed properly.
"multinli" dataset (KorNLI/multinli.train.ko.tsv) is not used in huggingface datasets due to related error, (see https://huggingface.co/datasets/kor_nlu/blob/main/kor_nlu.py#L28) and for the same reason, the number of data in testset is treated differently from published one.