Skip to content
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

cannot pull - tx ERROR: not enough values to unpack (expected 2, got 1) #346

Open
evgenyfadeev opened this issue Apr 23, 2023 · 2 comments

Comments

@evgenyfadeev
Copy link

Hello, when I run tx pull or tx status, I'm getting the error "tx ERROR: not enough values to unpack (expected 2, got 1)"

tx --version: 0.14.4, py 3.9, x86_64

Here is my .transifexrc:

[https://www.transifex.com]
api_hostname = https://api.transifex.com
hostname = https://www.transifex.com
password = <api token>
rest_hostname = https://rest.api.transifex.com
token = <api token>
username = api

.tx/config:

[main]
host = https://www.transifex.com

[o:askbot:p:askbot:r:askbot-translation-part1-main]
file_filter = askbot/locale/<lang>/LC_MESSAGES/django.po
source_file = askbot/locale/en/LC_MESSAGES/django.po
source_lang = en
type = PO
resource_name = askbot-translation-part1-main

[o:askbot:p:askbot:r:askbot-translation-part2-js]
file_filter = askbot/locale/<lang>/LC_MESSAGES/djangojs.po
source_file = askbot/locale/en/LC_MESSAGES/djangojs.po
source_lang = en
type = PO
resource_name = askbot-translation-part2-js
@evgenyfadeev evgenyfadeev changed the title tx ERROR: not enough values to unpack (expected 2, got 1) cannot pull - tx ERROR: not enough values to unpack (expected 2, got 1) Apr 23, 2023
@evgenyfadeev
Copy link
Author

evgenyfadeev commented Apr 23, 2023

Haha, now I get it - this one is deprecated.

Perhaps it's a good idea to put scary depecation emojis on the README and on the Pipy page - like a big stop sign.

Even thought the readme text does mention the new version, the title is "The New Client 🎉" - does not give an impression that this code should no longer be used.

@keithbowes
Copy link

Yeah, during the deprecation period, tx would show deprecation warnings every time you tried to do something and then one day, it stopped working entirely and I had to migrate to the new client. It's unfortunate that no one has forked this and updated it to the new API, for those who want to continue using the Python version (though, from a user's perspective, there's very little difference between the Python and Go versions, but as you say, getting it from Pipy no longer works, and a lot of OSes still have the old version in their repos).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants