Parser library for Swiss ESR (“Einzahlungsschein mit Referenznummer”) account statement records.
Features
Support for type 3 and 4 records (automatically detected)
Implements various integrity checks according to record description manual
Converts values to int, Decimal, etc.
Getting started
Read data from a ESR file (usually ending with *.v11):
from esr import ESR
with open('esr_file.v11', 'r') as f:
data = f.read()
statement = ESR.parse(data)
for record in statement.records:
print(record.amount)
print(statement.total_record.amount)
Metadata
Release files for python-esr 0.2
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 | Actions |
|---|---|---|---|---|
| python-esr-0.2.tar.gz | 17.9 kB | Without provenance | Details for python-esr-0.2.tar.gz |
Release files / python-esr-0.2.tar.gz
| Download URL | python-esr-0.2.tar.gz |
|---|---|
| Size | 17.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d918baf5b8fab97f1d0cca09d0331e2e56f19caa55a8cc3c940e0ba827850b0f
|
|
BLAKE2b-256 checksum How to use checksums |
911e9c3a3df9c242427928f0804137f2918584cd972cf2e0253c99024448bc2c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for python-esr 0.2
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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.