-
Notifications
You must be signed in to change notification settings - Fork 282
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
Fix for INVALID_SIGNATURE in python3.x.x #158
Conversation
Thanks, @ericsomdahl are you maintaining the project? |
@bitfag still here -- just slow to get around at the holiday season. I am ok with this fix but the build is broken due to the new USD markets added recently. I can get to the fix for the build once my holiday starts, in a few days. in the meantime I will merge this knowing that the pypy build will not propagate out. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
I'm still getting the INVALID_SIGNATURE with API 2.0 even with @forgetso 's fix in the latest version of python-bittrex. Am I doing something wrong? It seems like the issue is that I'm using windows. Works fine on linux |
@brotolisk Unfortunately, I don't have windows to check this out but glad you figured it out. |
Hi, thank you guys a lot for keeping this repo up to date!!
My OS is Ubuntu 18.04 |
@Ben0n I have no problems on API v1.1 |
@bitfag thanks for your reply! API v1.1 is working fine for me too, but since I want to place a stop-loss order via the API I would need to use the API v2.0 |
@Ben0n can't say anything about 2.0, I'm sticking to v1.1 as officially supported. |
@Ben0n Try using
but the equivalent for sell which is .sell_limit. |
@ericsomdahl @Ben0n Sincere apologies, it seems like I had falsely attributed the disappearance of INVALID_SIGNATURE in the response to my change to python-bittrex. However, it seems that buy_limit works in python3 but trade_buy does not. @ericsomdahl you may wish to revert this change as it effectively does nothing.
|
I have the same problem here. Want to use API 2.0 but I keep getting INVALID_SIGNATURE errors. My setup: python --version # Python 2.7.10 Testing with python3 (Python 3.7.0) shows no difference (the packages are of the same versions). I also tried different python versions using docker images - to no avail. Is there anyone for whom API 2.0 calls still work? Or any other ideas why API 2.0 does not work? my test code:
|
Fix for INVALID_SIGNATURE in python3.x.x (ericsomdahl#158)
This is related to the following issue #136