Skip to content

Conversation

alixdamman
Copy link
Collaborator

I chose the same logic as Numpy: use NaN in docstrings and nan when printing values.

Pandas chose to use NaN everywhere.

@alixdamman alixdamman requested a review from gdementen April 11, 2019 09:11
Copy link
Contributor

@gdementen gdementen left a comment

Choose a reason for hiding this comment

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

I am very surprised there are only 2 occurrences to changes?!?

@gdementen
Copy link
Contributor

otherwise LGTM (and should not even require a review)

@alixdamman alixdamman force-pushed the master branch 3 times, most recently from 9264074 to 01669f2 Compare May 10, 2019 10:03
@gdementen
Copy link
Contributor

Is there anything left to do before you can merge this?

@alixdamman alixdamman added this to the 0.31 milestone May 27, 2019
@alixdamman
Copy link
Collaborator Author

I am still not sure about the strategy to adopt with the NaN in the documentation. I prefer to move this issue to the 0.31 milestone

@gdementen
Copy link
Contributor

What's the problem exactly?

@alixdamman
Copy link
Collaborator Author

If we except the doctests, both Numpy and Pandas use NaN in their documentation.
When it comes to display the "NaN" values, Numpy prints nan and Pandas NaN.

In our case, since the raw data are stored in Numpy ndarray, I think we should the same strategy as Numpy.

…ep nan when printing values. (same as Numpy).
@alixdamman alixdamman force-pushed the 335_standardize_nan_in_docstrings branch from ec739af to a62c32d Compare August 5, 2019 08:25
@alixdamman alixdamman merged commit ecbb3c7 into larray-project:master Aug 5, 2019
@alixdamman alixdamman deleted the 335_standardize_nan_in_docstrings branch August 5, 2019 08:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants