Pandas 2.0.0 Compatibility with read_csv #420
Merged
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.
Revision from previous closed PR
Pandas 2.0.0 was released today. A new argument called
dtype_backend
was added to theread_csv()
function that appears to affect the default behavior when reading null values.When the
master.csv
files are read with Pandas 2.0.0, the string value"None"
now appears to be parsed by default toNaN
. This is problematic in places where themeta_info
dictionary's propertiesadditional edge files
andadditional node files
are checked to be"None"
.see lines 106 and 111 in ogb/linkpropped/dataset.py:
The easiest way to fix this in the latest version that preserved compatibility with previous versions was to add
keep_default_na=False
when the csvs are read.Also very minor fix of inconsistency of the
has_edge_attr
property of theogbl-vessel
dataset, which was set toFalse
in themake_master_file.py
but is True in the latest csv file committed here.