Feature seconds/days precision support #21
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
added 2 commits
July 27, 2015 11:32
…r than the default microseconds.
Conflicts: docs/index.rst tox.ini
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 have to deal with a bunch of legacy databases which have durations stored as both seconds and days - they are appropriate values given the intention thus I don't think it should be expected the underlying data should change (it can't, they are legacy, closed source apps that can't be changed).
Thus, I've added support for days and seconds.
In the process I've also updated the tox.ini to support various other configurations (ie.. python 2.6, 3.3, 3.4 and pypy) and all tests are passing for all environments.