Flit gettext
Compiling gettext i18n messages during project bundling.
"Binary files should never be committed to a repository to promote transparency and security." That is why this project was created.
Usage
Simple, just add flit-gettext to your pyproject.toml
build-system requirements and set the build-backend:
# pyproject.toml
[build-system]
requires = [
"flit-gettext[scm]", # [scm] is optional
# …others, like wheel, etc.
]
# using flit-core as a base build-backend
build-backend = "flit_gettext.core"
# or using flit-scm as a base build-backend for git-based versioning
build-backend = "flit_gettext.scm"
# To use use flit-scm, you will need to include the optional dependency above.
Please make sure, your build system has gettext installed.
If you ship wheels, those will include the compiled .mo files.
That's it!
Metadata
Release files for flit-gettext 1.1.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 | |
|---|---|---|---|---|
| flit_gettext-1.1.0.tar.gz | 4.0 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| flit_gettext-1.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 8.5 kB
Release files / flit_gettext-1.1.0.tar.gz
| Download URL | flit_gettext-1.1.0.tar.gz |
|---|---|
| Size | 4.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c417373cd014218d74b88eb1383a0849c391c07a946e180fd659744b56200579
|
|
BLAKE2b-256 checksum How to use checksums |
6f1b62866dc3030733717e9f974cba0cc7fb10934f9b592458a08beb4b45f634
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 11, 2026.
Transparency logRelease files / flit_gettext-1.1.0-py3-none-any.whl
| Download URL | flit_gettext-1.1.0-py3-none-any.whl |
|---|---|
| Size | 4.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ec43db845b5305994c8c551c0a8edab50284be4d9e96ace9a99f5924e28eb772
|
|
BLAKE2b-256 checksum How to use checksums |
8f40cdb6917d72424c37549a912d4d58d38fa0405d870a780328c4445dc3a3f5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 11, 2026.
Transparency logSecurity for flit-gettext 1.1.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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for flit_gettext-1.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 11, 2026.
Transparency logA 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.