Releases: Psiphon-Inc/transifexlib
v4.0.0
Improvements to the output mutators necessitated a change in function signature, so this is getting a new major version.
It is strongly recommended that consumers of this library upgrade, as it includes fixes.
Full Changelog: v3.0.0...v4.0.0
NOTE: This is unrelated to this release, but at that this time the transifex-python library does not work with Python>=3.12. The issue (which has no traction) is here. For now you'll need to use an older Python.
On Windows, with Scoop, this can be done like so:
c:\Users\<user>\scoop\apps\python\3.11.5\python.exe -m pipenv install --ignore-pipfile
v3.0.0
Updated to use Transifex API v3.
Breaking change: The first argument to process_resource
is the resource URL rather than just the slug.
To update the version of this library, run:
$ pipenv --rm
$ pipenv update --ignore-pipfile transifexlib
(If you're using a different package manager, adjust accordingly.)
Edit: The above pipenv doesn't seem to work now. Try this:
$ pipenv --rm
$ pipenv run pip install git+https://github.com/Psiphon-Inc/transifexlib.git
$ pipenv lock
Modify your process_resource
call(s) to pass the resource URL in the form:
https://www.transifex.com/<organization>/<project>/<resource>/
v2.0.0
Use a Transifex API token for access rather than username and password.
Upgrade steps:
- Generate a Transifex API token.
- Copy token value and save into a file named
transifex_api_token
in the same directory astransifex_pull.py
. (It can be anywhere and named anything, but then the file path has to be supplied totransifex_pull.py
.) - Delete
transifex_conf.json
from thetransifex_pull.py
directory (or wherever it was stored -- again, it could have been supplied to the script via an argument). - Add
transifex_api_token
to.gitignore
. - Run
pipenv update transifexlib
to update transifexlib inPipfile.lock
. - Run
pipenv --rm
to destroy your current pipenv environment. - Run
pipenv install --three --ignore-pipfile
to reinstall the environment. - Commit
.gitignore
andPipfile.lock
.
(Deleting and reinstalling the env shouldn't be necessary, but it seems to be. And isn't such a big hassle.)
You should now have an updated transifexlib and be ready to run. (You can check that transifexlib is updated by inspecting Pipfile.lock
and seeing if transifexlib.ref
is ee9c87e4efa7824b020765031cfa46f0f921b5ea
. Or just running it and seeing if it picks up the API token properly.)