Pluralization bug with Duration.in_words() #826
Merged
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
VascoSch92
reviewed
May 20, 2024
Co-authored-by: Vasco Schiavo <[email protected]>
ashb
reviewed
Jul 16, 2025
ashb
reviewed
Jul 16, 2025
ashb
reviewed
Jul 16, 2025
Separating out fix from adding seoncds_n_decimal
CodSpeed Performance ReportMerging #826 will not alter performanceComparing Summary
|
ashb
reviewed
Jul 16, 2025
ashb
reviewed
Jul 16, 2025
ashb
reviewed
Jul 17, 2025
ashb
approved these changes
Jul 17, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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 noticed that
Duration(milliseconds=10).in_words()would return0.01 secondwhen it should be0.01 seconds. So I fixed that but also realized that sometimes people might want a bit more precision so I added a keyword argseconds_n_digitswith a default value of 2.