This repository has been archived by the owner on Oct 29, 2024. It is now read-only.
Adjustments to deal with time precision rounding errors in _convert_dataframe_to_json() #346
Conversation
This file contains 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
…ataframe_to_json()
auphofBSF
added a commit
to auphofBSF/influxdb-python
that referenced
this pull request
Oct 14, 2018
extensive but not fully tested, unittests updates to follow also fixes ( influxdata#527,influxdata#489, influxdata#346, influxdata#344, influxdata#340)
|
Thank you so much for contributing this PR @hirochri but need to close this in lieu of more recent changes to the codebase. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
I believe this fixes issues 344 and 340 with timestamps rounding weirdly when nanosecond (or None) time precision is specified