PyMBFL
pymbfl provides Python bindings for libmbfl. libmbfl is used to determine encoding of the files; it tries to guess the right encoding depending on the list of the encodings which user wants to check.
Typical pymbfl usage:
>> import pymbfl
# Collect information about encoding
>> encoding = pymbfl.Encoding("ascii")
>> bool(encoding.flags & pymbfl.MBCS)
False
>> encoding.mime
'US-ASCII'
>> encoding.aliases
['ANSI_X3.4-1968', 'iso-ir-6', 'ANSI_X3.4-1986', 'ISO_646.irv:1991',
'US-ASCII', 'ISO646-US', 'us', 'IBM367', 'IBM-367', 'cp367', 'csASCII']
# Determine possible encoding
>> language = "ru"
>> encodings = ["UTF-8", "UTF-16", "UTF-32LE"]
>> detector = pymbfl.Detector(language, encodings)
>> detector.detect(data, strict) # enable/disable strict check and detect
See docs/pymbfl.html file for more detailed description.
1 maintainer
Metadata
1 maintainer
Release files for pymbfl 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 | |
|---|---|---|---|---|
| pymbfl-0.2.tar.gz | 22.0 kB | Without provenance | Details |
Release files / pymbfl-0.2.tar.gz
| Download URL | pymbfl-0.2.tar.gz |
|---|---|
| Size | 22.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
84a4e6cbdda4ea65824c06a50f2625ba005b1a24d9eafcf853023b26f8c3e7af
|
|
BLAKE2b-256 checksum How to use checksums |
2d4373728d7519fdd025a2cab4b96fd5790ddaaf6bbc86a8dc06ca524fff0639
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for pymbfl 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.
