DOC: actually document float_precision in read_csv #13377
Closed
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
gfyoung
changed the title
gfyoung
force-pushed
the
float-precision-doc
branch
from
ffca1ec to
a9eed16
Compare
Current coverage is 84.23%@@ master #13377 diff @@
==========================================
Files 138 138
Lines 50739 50739
Methods 0 0
Messages 0 0
Branches 0 0
==========================================
Hits 42740 42740
Misses 7999 7999
Partials 0 0
|
|
ty |
22 tasks
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.
So I wasn't 100% correct when I said that
float_precisionwas documented here. It was well documented internally forTextParserand in a section forio.rst, but it wasn't listed formally in the parameters for theread_csvdocumentation.