bleutrade, anxpro and southxchange withdraw() with Python 2.7 ccxt 1.9.175

It looks like the withdraw method for bleutrade is calling an unsupported dictionary key (uuid). Am I understanding correctly that it’s mostly mirroring bittrex with a few exceptions?

When I directly run this code:

result = bleutrade.accountGetWithdraw(bleutrade.extend({
            'currency': 'ETH',
            'quantity': 0.1,
            'address': '0x27b8F8D78742C47979dE46862696F39427f82995',
        },))
print result

I get this result: {u'message': u'Your withdraw has been successfully scheduled.', u'result': [], u'success': u'true'}

It looks like bleutrade doesn’t provide a transaction id? So I think we should change ‘uuid’ to, perhaps, ‘message’? Then we at least get something back when executing a withdrawal and no error.

    def withdraw(self, currency, amount, address, params={}):
        self.load_markets()
        response = self.accountGetWithdraw(self.extend({
            'currency': currency,
            'quantity': amount,
            'address': address,
        }, params))
        return {
            'info': response,
            'id': response['result']['message'],
        }

I would try the pull request stuff… except I’m not certain this is a desired change for everyone. Let me know your thoughts, Thanks!

[PhinixPhire]

Here’s what I did, in case it’s helpful to future readers… this way the script at least carries something through to describe what may have happened with the withdrawal when reviewing the ledger (I log trxid to a database for historical reference)

import sys
try:
  trxid = y.withdraw('ETH', amount, wallet).get('id')
except:
  trxid = str(sys.exc_info()[0]) + " occured. Funds may have withdrawn anyway."

The withdrawal does still complete. I’ve done several tests.

[PhinixPhire]

Cool. I will be happy to work within that paradigm then. I’m sure I can patch a workaround for my local scripts.