unrfc2047: a decoder for RFC2047 (MIME Part 3) encoded text.
Latest release 20200524: Handle unknown charsets (parochially and abitrarily) and other decode failures.
Function unrfc2047(s)
Accept a string s containing RFC2047 text encodings (or the whitespace
littered varieties that come from some low quality mail clients) and
decode them into flat Unicode.
See http://tools.ietf.org/html/rfc2047 for the specification.
Release Log
Release 20200524: Handle unknown charsets (parochially and abitrarily) and other decode failures.
Release 20171231: Change final .decode to use "replace". Fix a bunch of warning format strings.
Release 20170904: Initial PyPI release.
1 maintainer
Metadata
1 maintainer
Release files for cs.rfc2047 20200524
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 |
|---|---|---|---|---|
| cs.rfc2047-20200524.tar.gz | 3.0 kB | Without provenance | Details for cs.rfc2047-20200524.tar.gz |
Release files / cs.rfc2047-20200524.tar.gz
| Download URL | cs.rfc2047-20200524.tar.gz |
|---|---|
| Size | 3.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fb9000983cec6840e83d7bac404235a7a13c39be007d1916c2fc6b39fa426a2c
|
|
BLAKE2b-256 checksum How to use checksums |
7507c6bf2424bfad4aac8f06326a5acec4d94fedd4ce81a3c5b2b0493ccbd3e0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.23.0 setuptools/41.2.0 requests-toolbelt/0.9.1 tqdm/4.43.0 CPython/3.7.7
|
Security for cs.rfc2047 20200524
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.
