-
Notifications
You must be signed in to change notification settings - Fork 55
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
get_recent_trades crashes due to new column #76
Comments
Came here to report the same. :) |
Same here! Any solutions?? |
@Monolite , @smeingast , @JosorioData |
Could you tell us when this pull request would be available? Thank you So Much! I Need this for a project |
@JosorioData I have no idea, it appears that this project isn't alive. In the file pykrakenapi.py Hope that helps |
Im just starting, could you help me how to do that??? thanks in advance |
@JosorioData Of course I can... but it might be a bit complicated here. |
Could you tell me your email? so i cand send you a little nothebook |
@JosorioData email me at : [email protected] |
Apparently, kraken api has released a new version in which a new column has appeared, leading to api failure when setting trades.columns. After adding a new column name, api works properly, but can't tell what data was added.
Any suggestion on new column's naming? Looks like a consecutive value...
The text was updated successfully, but these errors were encountered: