Make possible to read from dbf’s with codepage unsupported by modules dbf and codecs (895 cz Kamenicky, ..)
import dbf
from dbf_read_iffy import fix_init, fix_895
fix_init(dbf)
t = dbf.Table('autori.dbf')
t.open('read-only')
for record in t:
print fix_895(record.autor)
t.close()
You can ignore Python 2.7 installation error in test_v3.py (from aenum which is requirement of dbf).
For 620 pl Mazovia: You can define conversion map in fix_620(). If possible please: Fork me, clone your fork, commit/push, generate Pull request from your fork. Thx.
Metadata
Release files for dbf_read_iffy 1.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 | |
|---|---|---|---|---|
| dbf_read_iffy-1.0.2.tar.gz | 2.6 kB | Without provenance | Details |
Release files / dbf_read_iffy-1.0.2.tar.gz
| Download URL | dbf_read_iffy-1.0.2.tar.gz |
|---|---|
| Size | 2.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dfdedb3ab4b693a352aac15439e1b513cc8ae240350c0746e34bcbc127ecc0f1
|
|
BLAKE2b-256 checksum How to use checksums |
5c0d7cfd2ebf357673ad7e468781e9238cf0b426d201b8508f141ddc6946ff4f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for dbf_read_iffy 1.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.