metric() adds a digit when a value rounds into quetta
Maintainers usually reply within 1 day
@SashaMIT is already working on this.
Since Oct 1, 2026.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 75/100
Research direction
Start with the metric() entry point and run the reproduction shown in the issue to confirm the quetta boundary behavior. Trace the rounding and prefix selection around 9.996e30 through 9.996e32, then verify that the output matches the four expected examples and preserves the existing 9999 result.
Written by the indexing model from the issue text.
Description
What did you do?
import humanize
print(humanize.metric(9.996e30))
print(humanize.metric(9.996e31))
print(humanize.metric(9.996e32))
print(humanize.metric(9999))
What did you expect to happen?
Three digits, same as 9999, which is already 10.0 k and not 10.00 k.
10.0 Q
100 Q
1.00 x 10³³
10.0 k
9.996e32 has no prefix after quetta, so scientific notation.
What actually happened?
10.00 Q
100.0 Q
1000 Q
10.0 k
The rounding carry stops at exponent 30. 2.596e32 is still 260 QF.
What versions are you using?
- OS: macOS
- Python: 3.14
- Humanize: main
- Dominant language
- Python
- Stars
- 768
- Forks
- 243
- Avg merge
- 4d 12h
- Merged PRs (30d)
- 19
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from python-humanize/humanize
-
intcomma returns exponential notation for large floatsPossibly taken @Omarinho12345 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
python-humanize/humanize#521 ·
Maintainers usually reply within 1 day
-
naturalsize() truncates non-integer byte counts below the base ("1 Bytes")May be free again A pull request for this issue was closed without being merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
python-humanize/humanize#459 · 2 comments ·
Maintainers usually reply within 1 day
-
intcomma returns scientific notation for large floatsPossibly taken @TheNetherWatcher claimed this 47 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
python-humanize/humanize#431 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 25/100
python-humanize/humanize#512 · 1 comment ·
Maintainers usually reply within 1 day
-
naturalsize() ignores the locale decimal separatorPossibly taken @ekanshul claimed this 29 days ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 55/100
python-humanize/humanize#460 ·
Maintainers usually reply within 1 day
All issues in python-humanize/humanize
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
mozilla-ai/cq#601 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
LUCJ pass manager raises NoEdgeBetweenNodes when an edge is bad for two two-qubit gatesPossibly taken @hat-im claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
opensubtitlescom: provider rejects pt-PT even though its own converter maps itPossibly taken @paulo-0308 claimed this today. Open
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Diaoul/subliminal#1405 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100