This release is a pre-release and may not be stable for production use.
decimo
A drop-in replacement for Python's decimal, written in
Mojo.
⚠️ Development release. The API is settled enough to use, but the versions carry a timestamp:
0.15.0.devYYYYMMDDHHMMSS, where0.15.0is the version of the Mojo library the wheel packages. Wheels: macOS arm64 (11 and later) and Linux x86_64 and arm64 (glibc 2.35 and later), CPython 3.13 and 3.14. Everywhere else, build from source.
Change one import and your program keeps working:
# from decimal import Decimal, getcontext
from decimo import Decimal, getcontext
getcontext().prec = 50
print(Decimal(1) / Decimal(7))
# 0.14285714285714285714285714285714285714285714285714
The two libraries agree digit for digit. The test suite checks every
operation against the standard library rather than against a table of
expected strings, so "agrees with decimal" is a property that is measured,
not a claim.
How fast is it?
The same benchmark file run against both libraries --
python/benchmarks/compare.py in the repository, which imports one or the other
and runs identical code. Best of five, on an Apple M-series laptop:
| Program | decimo | decimal | |
|---|---|---|---|
| add/sub/mul/div, 28 digits | 90.6 ns | 73.0 ns | 1.24× slower |
| add/sub/mul/div, 200 digits | 331.8 ns | 409.0 ns | 1.23× faster |
| add/sub/mul/div, 1000 digits | 2.02 µs | 5.89 µs | 2.91× faster |
| compound interest, 150 years | 12.71 µs | 13.08 µs | about the same |
| e from its series, 500 digits | 197.92 µs | 162.75 µs | 1.22× slower |
| sqrt by Newton, 1000 digits | 143.29 µs | 232.29 µs | 1.62× faster |
| pi by Machin, 500 digits | 620.12 µs | 520.17 µs | 1.19× slower |
| parse and print, 1000 digits | 3.28 µs | 2.60 µs | 1.26× slower |
decimo is faster once the numbers are large, and 20-25% behind on small
ones. The small-number gap is not the arithmetic: measured against
libmpdec directly, without an interpreter in the way, decimo is 2-4× faster
at 9 digits on add, subtract, multiply and round, and faster at every
operation at 1000 digits. What is left is the
cost of the Python call itself -- building the result object and converting
the operands -- which CPython's decimal has had thirty years to shave. See
the benchmarks.
What works
Everything a decimal program normally touches:
- all the operators, including
//,%,divmod()and** getcontext().precandgetcontext().rounding,setcontext(),localcontext()(with keyword overrides),Contextobjects- all the rounding modes:
ROUND_HALF_EVEN,ROUND_HALF_UP,ROUND_HALF_DOWN,ROUND_DOWN,ROUND_UP,ROUND_CEILING,ROUND_FLOOR, exact for arithmetic,quantize,round()andto_integral_value() int(),float(),round(),math.floor/ceil/trunc,hash(),format()Contextyou can compute with:ctx.divide(x, y),ctx.sqrt(x),ctx.quantize(x, y)and the rest, none of them touching the current context- keyword arguments where
decimaltakes them:quantize(exp, rounding=ROUND_HALF_UP),to_integral_value(rounding=...),sqrt(context=...) Decimal((sign, digits, exponent)), soas_tuple()round-tripspow(x, y, modulus), by modular exponentiationquantize,normalize,as_tuple,as_integer_ratio,compare,fma,sqrt,exp,ln,log10,scaleb,adjusted,copy_abs,copy_negate,copy_sign,same_quantum,to_eng_string,max,min- the rest of the specification's surface:
remainder_near,next_plus,next_minus,next_toward,shift,rotate,logical_and,logical_or,logical_xor,logical_invert,logb,compare_total,compare_total_mag,compare_signal,max_mag,min_mag,number_class,to_integral_exact,is_normal,is_subnormal,from_number - the same coercion rules:
intconverts in arithmetic,floatdoes not, and both convert in a comparison copy,deepcopyandpickleZeroDivisionErrorwhere you expect it, and hashes that agree withint,floatanddecimal.Decimal
Four things decimal does not have
decimo.pi(1000) # 1000 digits of pi, by Chudnovsky with binary splitting
decimo.e(50) # 50 digits of e
Decimal(2).sqrt(rounding=ROUND_FLOOR) # and exp, ln, log10 too
Decimal(1).sinh() # and fifteen more, listed below
pi() and e() use the context precision when given no argument; decimal
has neither, and its documentation gives a recipe to write your own.
The mathematics is sin, cos, tan, arctan, arcsin, arccos,
arctan2, expm1, log1p, hypot, sinh, cosh, tanh, arcsinh,
arccosh and arctanh. Each takes the context precision and an optional
rounding=, like the four above, and each is correctly rounded. arctan2
and hypot take the second value first: y.arctan2(x) is atan2(y, x), and
x.hypot(y) is the hypotenuse. expm1 and log1p are there for the same
reason math has them -- near zero they keep the digits that exp(x) - 1
and ln(1 + x) lose.
rounding= on sqrt, exp, ln and log10 is decimo's own: decimal
ignores the context mode for these and always rounds half to even. And the
answer under any mode is decided rather than approximated. The library
computes wider than you asked, takes the interval its own error bound allows,
and checks that the whole of it rounds to one answer; if a boundary falls
inside, it widens and looks again. The same check now guards the default half
to even, where before the last digit was assumed rather than known -- so
ROUND_FLOOR really does stay under the true value, and a tie really is a
tie.
A second type for money
Decimal is arbitrary precision and is what a program reaching for
decimal.Decimal wants. Decimal128 is the other one: 96 bits of
coefficient and a scale from 0 to 28, in sixteen bytes that own nothing --
the layout .NET's System.Decimal and Rust's rust_decimal use.
from decimo import Decimal128 # Dec128 is the same type
price = Decimal128("19.99")
line = (price * 3).quantize(Decimal128("0.01")) # 59.97
Decimal128(2).sqrt() # and exp, ln, log10, sin, cos, tan
Decimal128("1").to_ieee754() # the IEEE 754 interchange bytes
It does arithmetic, compares, hashes and rounds like Decimal, mixes with
int, float and str on either side of an operator, and converts both ways
(Decimal128(x).to_decimal(), Decimal(x)). Its results never allocate, so it
is quicker than Decimal on every operation where the values are money and the
shape of them is known, and quicker than decimal on all of them but str().
A mixed expression settles in the wider type: Decimal128(x) + Decimal(y) is
a Decimal, either way round, because widening loses nothing.
What it does not do: it stops at 7.9E+28 and 28 decimal places and raises
rather than rounding into a context, it has no Context of its own beyond
the rounding mode, and its scale is never negative -- Decimal128("1.23E+5")
is 123000, where decimal keeps a coefficient of 123 with an exponent of 3
and can print it as 123E+3. Decimal128(0.1) is 0.1 rather than the whole
binary expansion, since 55 digits do not fit 28; what is promised is that
float(Decimal128(x)) == x.
What does not
decimo refuses these rather than answering differently:
- NaN and infinity. decimo has no non-finite values.
is_nan()andis_infinite()are alwaysFalse. ROUND_05UP. Nothing implements it; setting it raisesNotImplementedError.sqrt,exp,lnandlog10ignore the context rounding, as they do indecimal, and round half to even unless you passrounding=.**follows the context, also as indecimal. All of them are correctly rounded whichever mode applies, as are arithmetic,quantizeandround().//,%,divmod()andremainder_nearwith a long quotient.decimalraisesInvalidOperationwhen the integer quotient has more digits than the precision; decimo answers. The remainder is rounded to the context, as indecimal.Eminonly reaches four methods. Exponents are unbounded, soEminchanges nothing except whatnext_plus(0),next_minus(0),is_subnormal()andnumber_class()say, wheredecimal's answers need a smallest exponent.- Signals and traps.
Context.flagsandContext.trapsexist and stay empty.Inexact,Roundedand the rest are importable but never raised. Emin/Emax. Exponents are unbounded, so nothing ever underflows to zero or overflows to infinity. A loop that waits for a term to become exactly zero will not stop; wait for the sum to stop changing instead.- One context per process, not per thread.
DivisionByZero and InvalidOperation are aliases for ZeroDivisionError
and ValueError, which is what decimo actually raises, so except clauses
written against decimal still catch.
Installing
pip install decimo
Wheels are built for macOS arm64 (macOS 11 and later) and for Linux on x86_64 and arm64 (glibc 2.35 and later), for CPython 3.13 and 3.14. On anything else, build from source with pixi:
git clone https://github.com/forfudan/decimo && cd decimo
pixi run -e py314 release # or py313; the wheel lands in python/dist/
pip install python/dist/*.whl
Links
1 maintainer
Metadata
1 maintainer
Release files for decimo 0.16.0.dev20261016192933
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
| File | Reset | |||
|---|---|---|---|---|
| decimo-0.16.0.dev20261016192933-cp314-cp314-manylinux_2_35_x86_64.whl | CPython 3.14 | CPython 3.14 | Linux glibc 2.35+ x86-64 | Details |
| decimo-0.16.0.dev20261016192933-cp314-cp314-manylinux_2_35_aarch64.whl | CPython 3.14 | CPython 3.14 | Linux glibc 2.35+ ARM64 | Details |
| decimo-0.16.0.dev20261016192933-cp314-cp314-macosx_11_0_arm64.whl | CPython 3.14 | CPython 3.14 | macOS 11.0+ ARM64 | Details |
| decimo-0.16.0.dev20261016192933-cp313-cp313-manylinux_2_35_x86_64.whl | CPython 3.13 | CPython 3.13 | Linux glibc 2.35+ x86-64 | Details |
| decimo-0.16.0.dev20261016192933-cp313-cp313-manylinux_2_35_aarch64.whl | CPython 3.13 | CPython 3.13 | Linux glibc 2.35+ ARM64 | Details |
| decimo-0.16.0.dev20261016192933-cp313-cp313-macosx_11_0_arm64.whl | CPython 3.13 | CPython 3.13 | macOS 11.0+ ARM64 | Details |
Total release size: 9.3 MB
Release files / decimo-0.16.0.dev20261016192933-cp314-cp314-manylinux_2_35_x86_64.whl
| Download URL | decimo-0.16.0.dev20261016192933-cp314-cp314-manylinux_2_35_x86_64.whl |
|---|---|
| Size | 1.7 MB |
| Tags | CPython 3.14 Linux glibc 2.35+ x86-64 |
|
SHA-256 checksum How to use checksums |
3d52401a26093219d2dc52d8a61ccafb37e6d18bdf0937826544d1c5d6eab5d8
|
|
BLAKE2b-256 checksum How to use checksums |
074387588af73549c747e8b29b5ea46af493d3d91d3e462b0863f9b96e3c8859
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 16, 2026.
Transparency logRelease files / decimo-0.16.0.dev20261016192933-cp314-cp314-manylinux_2_35_aarch64.whl
| Download URL | decimo-0.16.0.dev20261016192933-cp314-cp314-manylinux_2_35_aarch64.whl |
|---|---|
| Size | 1.5 MB |
| Tags | CPython 3.14 Linux glibc 2.35+ ARM64 |
|
SHA-256 checksum How to use checksums |
42a3bdb7c00d86279dfaa108c31afe3c60de767659a70c0bdc0f108d73e25fa1
|
|
BLAKE2b-256 checksum How to use checksums |
105b4b989baea2156526d632a260e367f29629a194b55f905a21ee2b03c12071
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 16, 2026.
Transparency logRelease files / decimo-0.16.0.dev20261016192933-cp314-cp314-macosx_11_0_arm64.whl
| Download URL | decimo-0.16.0.dev20261016192933-cp314-cp314-macosx_11_0_arm64.whl |
|---|---|
| Size | 1.4 MB |
| Tags | CPython 3.14 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
af02cfad48f45dd09e6b1102fccdfc26c981891cf383fc7f516bd1b5ed5052db
|
|
BLAKE2b-256 checksum How to use checksums |
217285e9737dbd7d722d8e09b7f4bc6e28a3de398367d67f7dfc4104143a7c71
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 16, 2026.
Transparency logRelease files / decimo-0.16.0.dev20261016192933-cp313-cp313-manylinux_2_35_x86_64.whl
| Download URL | decimo-0.16.0.dev20261016192933-cp313-cp313-manylinux_2_35_x86_64.whl |
|---|---|
| Size | 1.7 MB |
| Tags | CPython 3.13 Linux glibc 2.35+ x86-64 |
|
SHA-256 checksum How to use checksums |
96581510563c313df3ed3edce47edffaf706f5e69c0ec615cccb1a80fe65f3cc
|
|
BLAKE2b-256 checksum How to use checksums |
6ac0a5bdebecc2cb5ff69cb17ec11f57eebe3d2d8c30c8ca078d3b175e3b041f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 16, 2026.
Transparency logRelease files / decimo-0.16.0.dev20261016192933-cp313-cp313-manylinux_2_35_aarch64.whl
| Download URL | decimo-0.16.0.dev20261016192933-cp313-cp313-manylinux_2_35_aarch64.whl |
|---|---|
| Size | 1.5 MB |
| Tags | CPython 3.13 Linux glibc 2.35+ ARM64 |
|
SHA-256 checksum How to use checksums |
c7afdf0d6343cebb97f92d582e97261b7383d79cce944a64736d39d9402729a8
|
|
BLAKE2b-256 checksum How to use checksums |
51053c4c188a9684ebf858cbc6895927cc8dc8cee9fdd6445ae531ead73e582a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 16, 2026.
Transparency logRelease files / decimo-0.16.0.dev20261016192933-cp313-cp313-macosx_11_0_arm64.whl
| Download URL | decimo-0.16.0.dev20261016192933-cp313-cp313-macosx_11_0_arm64.whl |
|---|---|
| Size | 1.4 MB |
| Tags | CPython 3.13 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
0594fa798a1a8a300bbab1bcd33ac0626691c2d91d47720f8c077de236901272
|
|
BLAKE2b-256 checksum How to use checksums |
e0b2d9a3dc708c32b7b499b84c4966369907e37370ecc244381515b80447303c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 16, 2026.
Transparency logSecurity for decimo 0.16.0.dev20261016192933
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 6 files in this release have been uploaded with provenance metadata.
Attestation for decimo-0.16.0.dev20261016192933-cp314-cp314-manylinux_2_35_x86_64.whl
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 16, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
