Skip to content

DOC: Better explain the behaviour of na_values #10488

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

Merged
merged 1 commit into from
Jul 2, 2015
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions doc/source/io.rst
Original file line number Diff line number Diff line change
Expand Up @@ -115,7 +115,7 @@ They can take a number of arguments:
as the index.
- ``names``: List of column names to use as column names. To replace header
existing in file, explicitly pass ``header=0``.
- ``na_values``: optional list of strings to recognize as NaN (missing
- ``na_values``: optional string or list of strings to recognize as NaN (missing
values), either in addition to or in lieu of the default set.
- ``true_values``: list of strings to recognize as ``True``
- ``false_values``: list of strings to recognize as ``False``
Expand Down Expand Up @@ -723,7 +723,8 @@ NA Values
~~~~~~~~~

To control which values are parsed as missing values (which are signified by ``NaN``), specifiy a
list of strings in ``na_values``. If you specify a number (a ``float``, like ``5.0`` or an ``integer`` like ``5``),
string in ``na_values``. If you specify a list of strings, then all values in
it are considered to be missing values. If you specify a number (a ``float``, like ``5.0`` or an ``integer`` like ``5``),
the corresponding equivalent values will also imply a missing value (in this case effectively
``[5.0,5]`` are recognized as ``NaN``.

Expand Down