Closed emmercm closed 6 years ago
The UnboundLocalError is masquerading an socket.error exception. I've fix the masquerading (in the dev branch), so you should get the actual error.
Function of why you get an error, we may need to change the socket errors handling. Normally, the only two error that are not cached are Resource temporarily unavailable
(which should not happend then reading) and premission denied
that tends to be a permanent error.
Maybe the full (real) traceback could help.
Sorry it took so long to publish the fixed version (from the dev branch), I have been very busy lately.
I'm getting this error frequently with Python 2.7.9 and btdht 0.3.1:
Using the example from the readme: