Fix docstring for na_values in parsers #10479
Merged
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
jreback
added a commit
that referenced
this pull request
Jul 1, 2015
Fix docstring for na_values in parsers
|
thanks! |
|
@jaidevd There are some other places in the docs were this is described (eg in io.rst). Would you like to adapt this as well? |
|
@jorisvandenbossche Sure. Give me a couple of hours. |
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.
I discovered entirely by accident that the
na_valuesinpd.read_*can be a string. According to the docstring, it can only be a sequence or a dict. This PR fixes that.