This is a tiny wrapper around the pyjavaproperties package that does unicode en- and decoding transparently.
The problem I tried to solve here is that Java Properties files only support ISO-8859-1 content. If you need unicode, you have to use something like native2ascii or propedit for Eclipse which converts content from unicode to ascii and stores it into the respective file. In Python, obviously, you want the actual unicode data and not the encoded version of the prop value and this is exactly what this here does.
To use it simply import the Properties class from the pyjavapropertiesu module instead of pyjavaproperties and use the getProperty method as before.
Please note, though, that the data within the internal dict in the Properties class is still encoded.
Metadata
Release files for pyjavaproperties-unicode 0.1.1
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 |
|---|---|---|---|---|
| pyjavaproperties-unicode-0.1.1.tar.gz | 2.0 kB | Without provenance | Details for pyjavaproperties-unicode-0.1.1.tar.gz |
Release files / pyjavaproperties-unicode-0.1.1.tar.gz
| Download URL | pyjavaproperties-unicode-0.1.1.tar.gz |
|---|---|
| Size | 2.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f0907dd52aafdcdcbceefd8c5655fd53293a38d40f94c748a2f8568edab3c059
|
|
BLAKE2b-256 checksum How to use checksums |
e51a04ddb674ed67f1808ece4f41f0131f166f9922a59568383938e1970ad205
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for pyjavaproperties-unicode 0.1.1
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.