marcx consists mainly of a pymarc.Record subclass called marcx.Record, that implements a few extra methods, which should ease MARC library metadata manipulations.
Documentation and examples can be found under: https://github.com/ubleipzig/marcx
1 maintainer
Metadata
1 maintainer
Release files for marcx 0.3.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 | |
|---|---|---|---|---|
| marcx-0.3.0.tar.gz | 30.0 kB | Without provenance | Details |
Release files / marcx-0.3.0.tar.gz
| Download URL | marcx-0.3.0.tar.gz |
|---|---|
| Size | 30.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f6380e5da575a1863c8889c610efc7c98c5af7c44d8ca7c9833047303fa85cc9
|
|
BLAKE2b-256 checksum How to use checksums |
55bd9eb7c0b73c14d9f1fe65047240e9e94ba20404b627f02c5dae0d98d463e4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.12
|
Security for marcx 0.3.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.
