This release is a pre-release and may not be stable for production use.
Forrin localization helpers
The goal of this project is to, eventually, provide i18n/L10n support for Python programs, complete with automatic conjguation, declension, and other word-morphing shenanigans in messages – preferably for all languages in the world.
The Translator class wraps gettext’s C-like API as one callable object, to be subclassed and instantiated in every module, and usually aliased to _.
Extraction methods are provided to detects calls to the _ function and store them in a POT file; the extractors will also play nicely with Babel’s setuptools hooks if you should choose to go in that direction.
When a traslated message begins with the “@” symbol, it becomes a Template, a unicode subclass which can do language-specific magic in its format() method.
Forrin uses UTF-8 exclusively.
Metadata
Release files for forrin 0.1-alpha
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 | |
|---|---|---|---|---|
| forrin-0.1-alpha.tar.gz | 8.9 kB | Without provenance | Details |
Release files / forrin-0.1-alpha.tar.gz
| Download URL | forrin-0.1-alpha.tar.gz |
|---|---|
| Size | 8.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0fa0869e62597a0baca34e9377b8c003593705c954e9514c4965ae90568a7ff8
|
|
BLAKE2b-256 checksum How to use checksums |
a3128e0818bb67d72330e174c9017825bd62337168f12393b27fa993948e8abb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for forrin 0.1-alpha
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.