POEditor sync
A commandline tool for synchronizing your project's translation with POEditor.
The script uses Click library to wrap POEditor API client into a commandline tool that can be used manually or inside shell scripts.
Installation
pip install poeditor-sync
Usage
Configuration
Create a config file poeditor.yml to link your project with a POEditor project and define paths to translation files. Multiple projects are supported.
api_token: ABC123...
projects:
- id: 12345
format: po
# set it to terms to order results by 'terms' alphabetically.
order: terms
# generic path to translation file
terms_path: locale/{language_code}/LC_MESSAGES/django.po
# alternatively, specify per-language path
terms:
en: locale/en/LC_MESSAGES/django.po
pl: locale/pl/LC_MESSAGES/django.po
- id: 54321
format: po
terms_path: locale/{language_code}/LC_MESSAGES/djangojs.po
terms:
en: locale/en/LC_MESSAGES/djangojs.po
pl: locale/pl/LC_MESSAGES/djangojs.po
If you're planning to commit the config file into your repository or share it with someone, it is recommend that the API token in your config file be a read-only token.
You can use a separate token for uploads and pass it using --token option or POEDITOR_TOKEN environment variable.
Commands:
# View usage instructions
poeditor --help
# generate config file
poeditor init {project-id}
# List projects and their translation languages
poeditor project-details
# download translations
poeditor pull
# Upload local translations to poeditor
poeditur push
# Upload only one language and user a different API token:
poeditur --language pl --token=123ABCD push
# Upload only terms (after adding new strings to the project)
poeditor push-terms --sync-terms --overwrite
Options
| Option | environment variable | default value | description |
|---|---|---|---|
--token |
POEDITOR_TOKEN |
api_token from config file | Authentication token for POEditor. Overrides value from config file. |
--config-file |
POEDITOR_CONFIG_FILE |
poeditor.yml | Path to the project config file in yaml format |
--language |
POEDITOR_LANGUAGE |
Operate only on this language |
Metadata
Release files for poeditor-sync 0.6
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 | |
|---|---|---|---|---|
| poeditor-sync-0.6.tar.gz | 5.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| poeditor_sync-0.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 12.6 kB
Release files / poeditor-sync-0.6.tar.gz
| Download URL | poeditor-sync-0.6.tar.gz |
|---|---|
| Size | 5.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e20168e8b4008b605eccc006ab3b47fdc291a8bf2a30a4f13e2c59c47427899a
|
|
BLAKE2b-256 checksum How to use checksums |
5870dcbb90f715ff9d7d57ebcc467f57ffa3410a71cb863279fbb9afde5e10a7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.7.17
|
Release files / poeditor_sync-0.6-py3-none-any.whl
| Download URL | poeditor_sync-0.6-py3-none-any.whl |
|---|---|
| Size | 7.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8a30334377dfc90d7e76302ea29ed47134ad64a30902dd48a0afcaa60c07883d
|
|
BLAKE2b-256 checksum How to use checksums |
36a1b003e4a1a970c0e4f501f027c30e30c475e5252d8a795eb754b517a799b9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.7.17
|
Security for poeditor-sync 0.6
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.