BUG: IndexError on read_csv/read_table when using usecols/names parameters and omitting last column #5767
Conversation
This file contains hidden or 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
This is an issue in read_csv/read_table where there is no header and both usecols and names and assigned but the last column is not included. This caused an IndexError after reaching the last column specified in usecols.
|
superceded by #5770, I cherry picked the test, Thanks |
ghost
closed this
wrenoud
deleted the
issue-5766-fix-read_csv-usecols-and-names-without-last-col
branch
This pull request was closed.
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 an issue in read_csv/read_table where there is no header and both usecols and names are assigned but the last column is not included. This caused an IndexError after reaching the last column specified in usecols. Existing test cases for
usecolswere modified to expose and address this specific issue.#5766