Use pip install i-texts
Requires:
- or
$TEXTS_PATH - or
$LOCALEand$LOCALES_PATH(default:./locales).
Loads texts from:
- or
$TEXTS_PATH - or {
$LOCALES_PATH}/{$LOCALE}.yml"
Example
from i_texts import texts
assert texts.dict == {1: "1", "a": "a", "words": "a b c", "ru": "русский"}
assert texts[1] == "1"
assert texts["a"] == "a"
assert texts.get_words("words") == ["a", "b", "c"]
1 maintainer
Metadata
1 maintainer
Release files for i-texts 0.2.0
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 |
|---|---|---|---|---|
| i-texts-0.2.0.tar.gz | 1.7 kB | Without provenance | Details for i-texts-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| i_texts-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for i_texts-0.2.0-py3-none-any.whl |
Total release size: 3.9 kB
Release files / i-texts-0.2.0.tar.gz
| Download URL | i-texts-0.2.0.tar.gz |
|---|---|
| Size | 1.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5649c0b1149dca33bfbab450588602450016b700aca6609b96f55d2c22fd4c8e
|
|
BLAKE2b-256 checksum How to use checksums |
9326a281dcd57c67b0db32770e5d8936ee689f4472453c37b708aa1d52b01d27
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
pdm/2.4.9 CPython/3.10.5
|
Release files / i_texts-0.2.0-py3-none-any.whl
| Download URL | i_texts-0.2.0-py3-none-any.whl |
|---|---|
| Size | 2.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f7f400ec9eac9156fe78d71dbbaec792b92f38fdcfe0b1fab2c009f111c69d97
|
|
BLAKE2b-256 checksum How to use checksums |
f559ef37a8f2e1d7103e9d613905d260fae667c2e8af4c01246bf0e7d1c8e6b7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
pdm/2.4.9 CPython/3.10.5
|
Security for i-texts 0.2.0
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.
