A buildout recipe to compile message catalog to binary format (.po to .mo).
Requirements
Usage
Minimal buildout config example:
[buildout] parts = po2mo [po2mo] recipe = c2c.recipe.msgfmt po-directory = foo/bar/i18n/ followlinks = false
The .mo files are created in the same directory as the .po files.
1 maintainer
Metadata
1 maintainer
Release files for c2c.recipe.msgfmt 0.2.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 | |
|---|---|---|---|---|
| c2c.recipe.msgfmt-0.2.2.tar.gz | 2.2 kB | Without provenance | Details |
Release files / c2c.recipe.msgfmt-0.2.2.tar.gz
| Download URL | c2c.recipe.msgfmt-0.2.2.tar.gz |
|---|---|
| Size | 2.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
109d064949b04f64c4273daf190fbe5215087d867169619ba3a9db47a2ae2b7e
|
|
BLAKE2b-256 checksum How to use checksums |
0c6e6e1e8c64dd137f2ec42f6f94d03037f8dc6b5f42b627b4921b8bdfd22fa5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for c2c.recipe.msgfmt 0.2.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.
