-
Notifications
You must be signed in to change notification settings - Fork 76
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
migrate to API version 3 due to v2 being deprecated #319
Comments
Hello, We are definitely aware that the Transifex Client needs to be updated to use the new API 3.0. I cannot give a timeframe for when it will be available, but we are very aware of the dates mentioned. Kind regards, |
Hello again, I wanted to inform everybody here that rewriting the Transifex Client to support APIv3 is a part of the Q2-2021 planned roadmap. Kind regards, |
Hello, An Alpha version of the aforementioned new client just went public. Feel free to check it out if you want; any feedback is more than welcome. Keep in mind it is an alpha release so we would not advise trusting it for production work. -k |
Is this the reason for
? |
I just received the email from Transifex about API versions 2 & 2.5 being deprecated. They'll be shut off in 2022-04-07.
Looking at
txlib/urls.py
it looks like thetransifex-client
is using API version 2. Obviously it'll need to be updated to v3 before April 2022.Filing this issue both to track the conversion & to raise awareness for users of
transifex-client
that they'll have to update before April 2022.The aforementioned email helpfully states:
True, but
transifex-client
isn't using API v3 yet; therefore updating doesn't actually help at the moment.The text was updated successfully, but these errors were encountered: