Allow timestamps to be in higher precision than seconds #38
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
Generate changelog in
|
maulik-doshi
changed the title
lauraAriasFdez
approved these changes
Jun 19, 2025
Contributor
lauraAriasFdez
left a comment
lauraAriasFdez
left a comment
There was a problem hiding this comment.
lgtm. Maybe it should be the opposite way try first with higher precission else default to lower precission
|
Released 0.24.0 |
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.
Before this PR
Timestamps could only be handled at the precision of seconds
After this PR
==COMMIT_MSG==
Timestamps can now be in the format with fractional seconds through Python datetime as many timestamps are.
==COMMIT_MSG==
Possible downsides?
Are Docs needed?