rphonenumbers
A drop-in replacement for phonenumbers
that runs parsing, formatting, validation and number matching on
rlibphonenumber, a Rust port of Google's
libphonenumber. Same functions, same signatures, same results, typically 10–70x faster.
rlibphonenumber does not cover all of phonenumbers: short numbers, as-you-type formatting, raw
metadata and the geocoder, carrier and timezone modules are missing. With the full extra,
rphonenumbers takes those from phonenumbers itself, so the whole API is available.
Status: alpha. Verified against
phonenumbers9.0.41.
Installation
pip install rphonenumbers # the Rust-backed core API
pip install "rphonenumbers[full]" # plus the rest of the phonenumbers API
Wheels are published for CPython 3.10+ and free-threaded CPython 3.14t on:
- Linux x86_64 and aarch64 (glibc 2.17+ and musl 1.2+)
- macOS x86_64 (10.12+) and arm64 (11.0+)
- Windows x64 and ARM64
On other platforms pip builds from the source distribution, which needs a Rust toolchain (1.88+).
Usage
Import it in place of phonenumbers:
import rphonenumbers as phonenumbers
x = phonenumbers.parse("020 8366 1177", "GB")
phonenumbers.format_number(x, phonenumbers.PhoneNumberFormat.E164) # '+442083661177'
phonenumbers.is_valid_number(x) # True
Or make every import phonenumbers in the process resolve to it, including imports inside
third-party libraries such as django-phonenumber-field:
import rphonenumbers
rphonenumbers.install() # call before those libraries are imported
import phonenumbers # -> rphonenumbers
The two packages can be installed side by side; nothing is shadowed unless you call install().
Libraries can use parts of the API that rlibphonenumber lacks. For example,
django-phonenumber-field's validate_phonenumber validator calls is_valid_short_number, so
install rphonenumbers[full] if you use it.
Performance
python benches/bench.py on an Apple M1 Max, CPython 3.14, phonenumbers 9.0.41:
| Operation | phonenumbers | rphonenumbers | Speedup |
|---|---|---|---|
parse("+1 650-253-0000") |
9.08 µs | 817 ns | 11.1x |
parse("020 8366 1177", "GB") |
11.65 µs | 822 ns | 14.2x |
format_number(E164) |
270 ns | 248 ns | 1.1x |
format_number(INTERNATIONAL) |
3.97 µs | 680 ns | 5.8x |
is_valid_number |
8.98 µs | 511 ns | 17.6x |
number_type |
8.75 µs | 507 ns | 17.3x |
| parse + validate + E164, 489 numbers across all regions | 69.7 ms | 998 µs | 69.8x |
PhoneNumberMatcher, 944 chars |
953 µs | 79 µs | 12.1x |
E164 formatting is already a string concatenation in phonenumbers, so there is nothing to win
there. The mixed-region batch gains the most because phonenumbers recompiles regexes once
Python's re cache (512 entries) overflows.
Compatibility
Implemented in Rust:
- Everything in
phonenumbers.phonenumberutil's public API:parse, allformat_*functions, validation, number types, matching, example numbers, region and calling-code queries,COUNTRY_CODE_TO_REGION_CODE,SUPPORTED_REGIONS, and so on. PhoneNumber,FrozenPhoneNumber,CountryCodeSource,NumberFormatandPhoneNumberDesc.PhoneNumberMatcher,PhoneNumberMatchandLeniency.
The functions accept any object with PhoneNumber's attributes, including upstream
phonenumbers.PhoneNumber instances.
Taken from phonenumbers when it is installed (rphonenumbers[full]), because the
rlibphonenumber crate does not provide them:
- The short-number API (
is_valid_short_number,expected_cost,is_emergency_number, ...). AsYouTypeFormatterandPhoneMetadata.- The
geocoder,carrierandtimezonemodules.
These run phonenumbers' own Python code and data, so they are no faster than in phonenumbers,
and they accept rphonenumbers' PhoneNumber objects. phonenumbers is loaded as a private copy
on first use, so this also works after install(). Without it, using these raises
AttributeError or ImportError explaining what to install.
A differential test suite
checks every public function against phonenumbers: about 6.7 million comparisons over the example
numbers of every region in many textual variants (national, international, IDD-prefixed, with
extensions, truncated, padded, shuffled), hand-written edge cases (RFC 3966 URIs, alpha numbers,
full-width and Arabic-Indic digits, invalid regions, oversized input), and every region and
calling code. Results, raised exception types and NumberParseException messages must all be
identical.
Known differences
example_number(None)returns a valid fixed-line example, but not necessarily the onephonenumberspicks: upstream returns the first hit while iterating aset, so its answer depends onPYTHONHASHSEED.format_out_of_country_keeping_alpha_chars(numobj, None)returns the international format;phonenumbersraisesAttributeErrorwhen the number hasraw_input.PhoneNumberMatcherscans the whole text on the firsthas_next()call rather than lazily; the sequence of matches is the same.min_candidate_lengthfilters on the matched string.parse(..., _check_region=False)(a private parameter) is accepted but ignored.NumberFormatpatterns passed toformat_by_patternrun on Rust'sregexengine, so Python-only syntax such as lookaround is rejected withre.error.- The APIs taken from
phonenumbersuse the metadata of the installedphonenumbersrelease. When it differs fromrphonenumbers.__phonenumbers_version__, their results can disagree with the core API on recently changed numbers.
Upstream fixes
rlibphonenumber 2.2.14 has three bugs that make its results differ from libphonenumber. This package corrects them itself until the fixes are released upstream:
is_valid_number_for_regiondoes not check that the number's country code belongs to the region, so+44 2423232345is reported valid forBS(vloldik/rlibphonenumber#35).format_by_patternrenders RFC 3966 extensions in national style (" ext. 42") instead of";ext=42"(vloldik/rlibphonenumber#36). rlibphonenumber inherits this from libphonenumber's C++ implementation, fixed there in google/libphonenumber#4087.format_out_of_country_keeping_alpha_charsemits" 247 40123"instead of"+247 40123"when the calling region has no single or preferred international prefix (vloldik/rlibphonenumber#37).
Development
Requires a Rust toolchain (1.88+):
pip install maturin
maturin develop --release
pip install pytest phonenumbers==9.0.41
pytest # API tests + differential tests against phonenumbers
python tests/differential.py # differential summary, per function
python benches/bench.py
The phonenumbers version used for testing must match the libphonenumber metadata release
bundled in rlibphonenumber (rphonenumbers.__phonenumbers_version__).
See RELEASING.md for how releases are published.
License
Apache-2.0. See NOTICE for attributions: the metadata and algorithms come from Google's libphonenumber via rlibphonenumber, and the Python API mirrors python-phonenumbers.
Metadata
Release files for rphonenumbers 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| rphonenumbers-0.1.0.tar.gz | 48.8 kB | Details |
Built distributions (wheels)
Total release size: 15.9 MB
Release files / rphonenumbers-0.1.0.tar.gz
| Download URL | rphonenumbers-0.1.0.tar.gz |
|---|---|
| Size | 48.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e689282f429a3bfc860e4ba54d0f85e4ca27ee15b0dbc07af5cf320b09f91ea9
|
|
BLAKE2b-256 checksum How to use checksums |
9784bddbb721e41d57e77411d9eb64051329947bdbc104f67af1264d4b0101a6
|
| 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 11, 2026.
Transparency logRelease files / rphonenumbers-0.1.0-cp314-cp314t-win_arm64.whl
| Download URL | rphonenumbers-0.1.0-cp314-cp314t-win_arm64.whl |
|---|---|
| Size | 860.9 kB |
| Tags | CPython 3.14 CPython 3.14 free-threading Windows ARM64 |
|
SHA-256 checksum How to use checksums |
f9e8ca643eff5b9be7aac3b2eabcc2520cdd99ace65d7d0b91f1f142e2bc3376
|
|
BLAKE2b-256 checksum How to use checksums |
4dc2a150cd000d49a3709099cdceafb9affd94ef18bffebb4f516272a6d109cb
|
| 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 11, 2026.
Transparency logRelease files / rphonenumbers-0.1.0-cp314-cp314t-win_amd64.whl
| Download URL | rphonenumbers-0.1.0-cp314-cp314t-win_amd64.whl |
|---|---|
| Size | 925.0 kB |
| Tags | CPython 3.14 CPython 3.14 free-threading Windows x86-64 |
|
SHA-256 checksum How to use checksums |
171113d8a55d86407e329846a784295fa9996d1498af2fd90704f6c8195fa4e8
|
|
BLAKE2b-256 checksum How to use checksums |
884cb050f9c4061585da135bb54b4a99afcc2391513513adfbf219ca185ac196
|
| 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 11, 2026.
Transparency logRelease files / rphonenumbers-0.1.0-cp314-cp314t-musllinux_1_2_x86_64.whl
| Download URL | rphonenumbers-0.1.0-cp314-cp314t-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 1.2 MB |
| Tags | CPython 3.14 CPython 3.14 free-threading Linux musl 1.2+ x86-64 |
|
SHA-256 checksum How to use checksums |
319e5618e49b32f6ce12115c651878686d35a14c2450bedacdd8c24bc57b39ac
|
|
BLAKE2b-256 checksum How to use checksums |
6d343da631b663a1dd1e0ad967a94e4933bc11f0f67ca8cc4607bc38ab908813
|
| 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 11, 2026.
Transparency logRelease files / rphonenumbers-0.1.0-cp314-cp314t-musllinux_1_2_aarch64.whl
| Download URL | rphonenumbers-0.1.0-cp314-cp314t-musllinux_1_2_aarch64.whl |
|---|---|
| Size | 1.1 MB |
| Tags | CPython 3.14 CPython 3.14 free-threading Linux musl 1.2+ ARM64 |
|
SHA-256 checksum How to use checksums |
57cfe28b0894618efc01ce812c1572ce524548c25d884adb38443862f8042b49
|
|
BLAKE2b-256 checksum How to use checksums |
144ea9220ad1595cdda1a11624c9181f0b7e66e9e0b1906be94b6d6aa0446fc8
|
| 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 11, 2026.
Transparency logRelease files / rphonenumbers-0.1.0-cp314-cp314t-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | rphonenumbers-0.1.0-cp314-cp314t-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 998.0 kB |
| Tags | CPython 3.14 CPython 3.14 free-threading Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
89cdf97c7d28ebb04cb5155e03e849d41fa129dbe909198d32aea01786e2e3a6
|
|
BLAKE2b-256 checksum How to use checksums |
86a8d644e542b5c4095a68006ebbc356d93372a628763726126e6638d52a98dd
|
| 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 11, 2026.
Transparency logRelease files / rphonenumbers-0.1.0-cp314-cp314t-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | rphonenumbers-0.1.0-cp314-cp314t-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 949.7 kB |
| Tags | CPython 3.14 CPython 3.14 free-threading Linux glibc 2.17+ ARM64 |
|
SHA-256 checksum How to use checksums |
0527df1ef02c08af07c0a41d902ee6ec943096a58ec461ea8d921607442648be
|
|
BLAKE2b-256 checksum How to use checksums |
c4935aa80a4d105473e7c164a9af25730fbdf1cfcc4a4f7eee7260a3e7bf66a0
|
| 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 11, 2026.
Transparency logRelease files / rphonenumbers-0.1.0-cp314-cp314t-macosx_11_0_arm64.whl
| Download URL | rphonenumbers-0.1.0-cp314-cp314t-macosx_11_0_arm64.whl |
|---|---|
| Size | 894.5 kB |
| Tags | CPython 3.14 CPython 3.14 free-threading macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
6eab3927bedff57a0d467e6f927399c5e3af17cb4af9c8f0f8f6afa45fba4610
|
|
BLAKE2b-256 checksum How to use checksums |
eaba9d5cc17ac92f77d2ce65be88b0c0ec3a7e67f6aa5d79c582e249de6a57a9
|
| 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 11, 2026.
Transparency logRelease files / rphonenumbers-0.1.0-cp314-cp314t-macosx_10_12_x86_64.whl
| Download URL | rphonenumbers-0.1.0-cp314-cp314t-macosx_10_12_x86_64.whl |
|---|---|
| Size | 947.8 kB |
| Tags | CPython 3.14 CPython 3.14 free-threading macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
217b92658ac1398df2a20d1352c729ffa92d92d670b7a985fecfddebe5c2dcfe
|
|
BLAKE2b-256 checksum How to use checksums |
fe69cc595946bb2c942b6928975d126e73ed52d39d19deb7b8dcafca06e41a76
|
| 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 11, 2026.
Transparency logRelease files / rphonenumbers-0.1.0-cp310-abi3-win_arm64.whl
| Download URL | rphonenumbers-0.1.0-cp310-abi3-win_arm64.whl |
|---|---|
| Size | 866.5 kB |
| Tags | CPython 3.10 Windows ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
b1e33cea6251b4642aba5dfbb3ff70e07ffa96de1d8449d64d8e255045440546
|
|
BLAKE2b-256 checksum How to use checksums |
19a46343edea4dc205b324e3a1b222b64ff46ebf789b4ed9a54cf1dd29455b39
|
| 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 11, 2026.
Transparency logRelease files / rphonenumbers-0.1.0-cp310-abi3-win_amd64.whl
| Download URL | rphonenumbers-0.1.0-cp310-abi3-win_amd64.whl |
|---|---|
| Size | 932.1 kB |
| Tags | CPython 3.10 Windows x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
6aa00c4fd42e8a8d4ed891a6d101d6c3f00a8da166f407c28ec6c8517e3655b8
|
|
BLAKE2b-256 checksum How to use checksums |
3cbbd22f581569e6753eb8c68059829cb05a7d1d2a5a65afd229b07f3476d0e0
|
| 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 11, 2026.
Transparency logRelease files / rphonenumbers-0.1.0-cp310-abi3-musllinux_1_2_x86_64.whl
| Download URL | rphonenumbers-0.1.0-cp310-abi3-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 1.2 MB |
| Tags | CPython 3.10 Linux musl 1.2+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
9bf945e54929185e71b388893ab6142e335dff160ab6c63e72e727a3e6bea5a7
|
|
BLAKE2b-256 checksum How to use checksums |
f293387f3b40b0739670f29666cdd0f937c81be8614b392922c9fdd6cc36e90b
|
| 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 11, 2026.
Transparency logRelease files / rphonenumbers-0.1.0-cp310-abi3-musllinux_1_2_aarch64.whl
| Download URL | rphonenumbers-0.1.0-cp310-abi3-musllinux_1_2_aarch64.whl |
|---|---|
| Size | 1.1 MB |
| Tags | CPython 3.10 Linux musl 1.2+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
ab754ef99c02baa43ec754ba4ace18c74171a25149a6fc169d0654d3bad1c07f
|
|
BLAKE2b-256 checksum How to use checksums |
7603190e57323f3d5c0acacfc924036c0bf071c7c45cd80e0ddff2963f6891b1
|
| 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 11, 2026.
Transparency logRelease files / rphonenumbers-0.1.0-cp310-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | rphonenumbers-0.1.0-cp310-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 1.0 MB |
| Tags | CPython 3.10 Linux glibc 2.17+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
7a9eec5f7b453652ad0ccb5e9d7c876fa69b59b1287ef5903d4fab178f96fc04
|
|
BLAKE2b-256 checksum How to use checksums |
7e2d172e66ea22571a12721185d403a2ca48edb52cb88cff1b937c8fc1f0d489
|
| 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 11, 2026.
Transparency logRelease files / rphonenumbers-0.1.0-cp310-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | rphonenumbers-0.1.0-cp310-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 952.6 kB |
| Tags | CPython 3.10 Linux glibc 2.17+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
80b234bfa696592ae163c5b68a209916e42d495d63c1ba9af34120dd3a452ab9
|
|
BLAKE2b-256 checksum How to use checksums |
64ab9d0f4145a54b220e2be68dec737fd42c190a78ddb63d18d8516297b5b0b5
|
| 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 11, 2026.
Transparency logRelease files / rphonenumbers-0.1.0-cp310-abi3-macosx_11_0_arm64.whl
| Download URL | rphonenumbers-0.1.0-cp310-abi3-macosx_11_0_arm64.whl |
|---|---|
| Size | 900.1 kB |
| Tags | CPython 3.10 abi3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
04937aa31106964cd83f0aaf85502cec9bd2376ae41329f7bfc925060a465a67
|
|
BLAKE2b-256 checksum How to use checksums |
43d574ee576a80c491932e66b84cdc9b28ffc0c7725ec3a83f2957d91ddc148f
|
| 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 11, 2026.
Transparency logRelease files / rphonenumbers-0.1.0-cp310-abi3-macosx_10_12_x86_64.whl
| Download URL | rphonenumbers-0.1.0-cp310-abi3-macosx_10_12_x86_64.whl |
|---|---|
| Size | 947.7 kB |
| Tags | CPython 3.10 abi3 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
e419b539aba35465b8945415bade9530f4aaddda8c73bf207bdfc6e70d7ecb48
|
|
BLAKE2b-256 checksum How to use checksums |
259d58bc050c770b7cc6c3754a60c013ee05e4b8a3936e3d1650e1772f66ddbf
|
| 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 11, 2026.
Transparency log