8000 consolidated the duplicate definitions of NA values (in parsers & IO) by OlegShteynbuk · Pull Request #16589 · pandas-dev/pandas · GitHub
[go: up one dir, main page]
Skip to content

consolidated the duplicate definitions of NA values (in parsers & IO) #16589

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.

Sign up for GitHub

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 14 commits into from
Jun 13, 2017
Merged

consolidated the duplicate definitions of NA values (in parsers & IO) #16589

Changes from 1 commit
Commits
Show all changes
14 commits
Select commit Hold shift + click to select a range
bc6752a
consolidated the duplicate definitions of NA values (in parsers & IO)
OlegShteynbuk Jun 3, 2017
0650da0
consolidated the duplicate definitions of NA values in parsers.pyx
OlegShteynbuk Jun 3, 2017
b0c1d4d
added blank lines - E302 expected 2 blank lines, found 1 in parsers.pyx
OlegShteynbuk Jun 3, 2017
1f0a350
added pesky blank lines - E302 expected 2 blank lines, found 1 in par…
OlegShteynbuk Jun 3, 2017
0579460
added pesky blank lines - E302 expected 2 blank lines, found 1 in par…
OlegShteynbuk Jun 3, 2017
6225c7c
changed to using existing function _ensure_encoded in parsers.pyx
OlegShteynbuk Jun 5, 2017
a7e7f01
reverted na_values.py back to using assert
OlegShteynbuk Jun 5, 2017
dc9a368
fixing typo
OlegShteynbuk Jun 5, 2017
e8f6e82
convert set to list
OlegShteynbuk Jun 5, 2017
5770506
put definition before reference
OlegShteynbuk Jun 5, 2017
5fa829e
import _NA_VALUES from common instead of parsers, make import explicit
OlegShteynbuk Jun 5, 2017
c499448
in import replace common with com
OlegShteynbuk Jun 5, 2017
03a335b
remove duplicate na values in in io.rst
OlegShteynbuk Jun 7, 2017
10cba2c
improved text related to na values in io.rst file
OlegShteynbuk Jun 9, 2017
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
Prev Previous commit
Next Next commit
remove duplicate na values in in io.rst
  • Loading branch information
@OlegShteynbuk
OlegShteynbuk committed Jun 13, 2017
commit 03a335b682bb1f4499b583bfc831e33b82b85dae
12 changes: 7 additions & 5 deletions doc/source/io.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -225,9 +225,8 @@ NA and Missing Data Handling

na_values : scalar, str, list-like, or dict, default ``None``
Additional strings to recognize as NA/NaN. If dict passed, specific per-column
NA values. By default the following values are interpreted as NaN:
``'-1.#IND', '1.#QNAN', '1.#IND', '-1.#QNAN', '#N/A N/A', '#N/A', 'N/A', 'n/a', 'NA',
'#NA', 'NULL', 'null', 'NaN', '-NaN', 'nan', '-nan', ''``.
NA values. By default the following values are interpreted as NaN: See :ref:`na values const
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The sentence "By default the following values are interpreted as NaN:" can be removed. I think

See :ref:`na values const <io.navaluesconst>` below for a list of the values interpreted as NaN by default.

<io.navaluesconst>` below.
keep_default_na : boolean, default ``True``
If na_values are specified and keep_default_na is ``False`` the default NaN
values are overridden, otherwise they're appended to.
Expand Down Expand Up @@ -1030,8 +1029,11 @@ the corresponding equivalent values will also imply a missing value (in this cas
``[5.0,5]`` are recognized as ``NaN``.

To completely override the default values that are recognized as missing, specify ``keep_default_na=False``.
The default ``NaN`` recognized values are ``['-1.#IND', '1.#QNAN', '1.#IND', '-1.#QNAN', '#N/A','N/A', 'NA',
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can you build the docs and show a rendering of this page. I think this might generate a build warning (and may not render correctly)

@jorisvandenbossche

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have build the docs locally before commit, there were warnings, some of them might be related to python 3, i have 2.7.13 on linux ; file doc/source/style.ipynb also was a problem, but the generated html looks ok, can not attach html file to this replay

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the only difference that i can see is a blank line because of the new label, but it might be not at bad thing at all, but i can remove the label and reuse the existing one that is for the heading NA Values, that will be several lines above

'#NA', 'NULL', 'NaN', '-NaN', 'nan', '-nan']``. Although a 0-length string

.. _io.navaluesconst:

The default ``NaN`` recognized values are ``['-1.#IND', '1.#QNAN', '1.#IND', '-1.#QNAN', '#N/A N/A', '#N/A', 'N/A',
'n/a', 'NA', '#NA', 'NULL', 'null', 'NaN', '-NaN', 'nan', '-nan', '']``. Although a 0-length string
``''`` is not included in the default ``NaN`` values list, it is still treated
as a missing value.

Expand Down
0