Noel Maersk

@philippose Thanks for your thoughts! I do tend to agree in general that it's "better" to scream loudly of a fault and do nothing when money is involved; however, the...

> Perhaps, if re-using the `PreparedRequest`, instead of constructing a new one in the except block... That is, if the `except` caught ~~a `502`~~ ~~a `504`~~ something that's known to...

**TL;DR:** `try/except` with `session.send()` in end-app works, but adds a lot of boilerplate (EDIT: and with a nasty repetition of in-lib code to catch subsequent exceptions). `retries` within lib approach...

@pawapps The "nonce window" part would make a good separate issue. ;) ----- As to network connection reliability: `v1` didn't gracefully handle the case where the remote "dropped" the connection...

It's been about a month of testing, and I haven't as-of-yet experienced a duplicate order when using the nonce-protection approach (see PR #65).

You probably mean using `k.balance()` instead of `k.query_public('Balance')`, and the like?.. Please give examples of what you propose. No need to flesh out over the entire Kraken API method space....

This is also mentioned in issue #11 (as the `query()` segment, and the only top-level question left unanswered there).

A few more thoughts: This would make sense as an extension of the base `API(object)` class, e.g. `ExtendedAPI(API)` or similarly named. The docstrings can't be copy-paste from Kraken's page (for...

> adhering to the names specified on the Kraken API guide would be best. Something like `k.get_trade_balance()` As to this point, IMO it does not hold. ["Get trade balance"](https://www.kraken.com/help/api#get-trade-balance) is...

Hey @dominiktraxl, that's pretty cool, and looks to me like exactly what @tasercake (and @jdddog?) were looking for! This seems about what I had in mind for `krakenex`: to be...