python-dateutil-rust
Pure-Rust port of the python-dateutil engine (rrule, relativedelta,
tz) plus the whole parser/isoparser path, with Python bindings
preserving the dateutil interface.
rustsmith Stage-1 mirror of dateutil/dateutil
(Apache-2.0), covering the recurrence/calendar/timezone engine and the
fuzzy/strict/ISO parse path (ADR-015 supersedes the ADR-013 parser
exclusion).
Layout: reusable core crate (dateutil-core, no Python dependency) plus a
thin PyO3 binding (dateutil._dateutil); src/dateutil/{rrule,relativedelta,tz/tz}.py
and src/dateutil/parser/{_parser,isoparser}.py are re-export shims over
the extension (_parser_py.py alongside is the verbatim upstream module
kept for the _tzparser lineage). Custom parserinfo subclasses and
tzinfos callables stay dynamic via the Info-trait/Python-callback seam
documented in src/parser_mod.rs. Two-track bench corpora + harness live
in bench_parser/ (manifest hashes frozen before measurement; workload
contract and repro command in bench_parser/WORKLOAD.md).
Measured performance
No accepted optimizations yet (mirror baseline); re-run release-prep after run --stage optimize merges winners.
Artifact hashes are intentionally absent here; see release-manifest.json.
1 maintainer
Metadata
1 maintainer
Release files for python-dateutil-rust 2.9.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 | Provenance | |
|---|---|---|---|---|
| python_dateutil_rust-2.9.0.tar.gz | 334.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| python_dateutil_rust-2.9.0-cp312-cp312-manylinux_2_34_x86_64.whl | CPython 3.12 | CPython 3.12 | Linux glibc 2.34+ x86-64 | Details |
Total release size: 1.3 MB
Release files / python_dateutil_rust-2.9.0.tar.gz
| Download URL | python_dateutil_rust-2.9.0.tar.gz |
|---|---|
| Size | 334.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
af63ff0276a90c8b67fa443549a0a9d1770f66d08eea5c5b5f2b1adf1e30e21c
|
|
BLAKE2b-256 checksum How to use checksums |
5ff03f7815f4f8c7c75d2695718518ff3c197e8dfdeeddbacddf97eefa9b44a2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.29 {"installer":{"name":"uv","version":"0.9.29","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / python_dateutil_rust-2.9.0-cp312-cp312-manylinux_2_34_x86_64.whl
| Download URL | python_dateutil_rust-2.9.0-cp312-cp312-manylinux_2_34_x86_64.whl |
|---|---|
| Size | 991.7 kB |
| Tags | CPython 3.12 Linux glibc 2.34+ x86-64 |
|
SHA-256 checksum How to use checksums |
b118df31eb5f7e77b616a3614d2f90016d81ee4815ca19ae17419600d8be9438
|
|
BLAKE2b-256 checksum How to use checksums |
4a5e26e71ca0971310bfa501452d1a6afec07d7889d5fcd348b28d5a290b782c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.29 {"installer":{"name":"uv","version":"0.9.29","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for python-dateutil-rust 2.9.0
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.
