mfup-core
MFUP/3 engine for streamed multipart uploads, durable receipts and interactive publication. The core supplies Engine, ProtocolError (code/status), relative_path, published_directory, AuthRequest, AuthResult, FileMapRequest, CommitEvent and StagedFile. Public hook types use TypedDict and the package includes py.typed.
The application chooses identity and scopes in authorize, which can return baseDir/targetDir, quotas, context, autoPublish and clientPublish per session. map_file maps metadata during manifest reception, before reading bodies. on_committed can read accepted files through list_staged/open_staged and return True to publish or False to leave server auto-publication disabled. Backend-only publication requires client_publish=False. Callback errors are represented separately from successful file acceptance and can be retried through retry_committed.
Payload staging and publication share the chosen session root; SQLite stays
in the Engine root. No Redis is required. Use one owning process; session
callbacks are not an exactly-once job queue. See the repository's
docs/EXTENDING.md for lifecycle, retries, errors and configuration details.
Metadata
Release files for mfup-core 3.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 | Provenance | |
|---|---|---|---|---|
| mfup_core-3.1.0.tar.gz | 14.5 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mfup_core-3.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 29.4 kB
Release files / mfup_core-3.1.0.tar.gz
| Download URL | mfup_core-3.1.0.tar.gz |
|---|---|
| Size | 14.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dca1e475c5d819a04fa22ec49fe03a978d5d6ef86671d3441c76e1d7666393e6
|
|
BLAKE2b-256 checksum How to use checksums |
7acd68e16ac261180375d91c8634abf669e0e17fb95743705d0753b1e8460565
|
| 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 Sep 10, 2026.
Transparency logRelease files / mfup_core-3.1.0-py3-none-any.whl
| Download URL | mfup_core-3.1.0-py3-none-any.whl |
|---|---|
| Size | 14.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
bf4454afb2780508422d0b72daced513ccac368c18bba4a69d0e805c3ce91d45
|
|
BLAKE2b-256 checksum How to use checksums |
1b9c45898bdcebcc018f256a8f6f864dcdb0b4ddf99f8fc0f69aaf2c5f01b613
|
| 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 Sep 10, 2026.
Transparency logSecurity for mfup-core 3.1.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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for mfup_core-3.1.0.tar.gz
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 Sep 10, 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.