Closed bradharmon closed 11 years ago
Thanks for reporting the problem. I'm away for work at the moment, will hopefully get to this in a couple of days.
Should be fixed now. Please reopen if the issue persists.
dont think this is fixed im seeing the same issue running python2.6 against unix python2.4 with your patch applied
@gregnwosu I can successfully connect a Python 2.6 to 2.4 interpreter. If you can provide a set of steps to reproduce the issue, someone may be able to help (I can't guarantee it'll be me, though).
I've done a little more investigation, it seems that these errors occur when connecting to python 2.3
Ive also observed strange behaviour when connecting from inside unit tests , especially using nose which tends to capture output streams
@gregnwosu Ah, that makes sense then; Pushy does not support 2.3 (or earlier). I don't recall the reason why. If it can be made to work with minimal changes, I'd probably accept a pull request.
Somewhere between pushy 0.5.1 and 0.5.3, creating a pushy connection fails with a local python version of 2.6.6 and a remote python version of 2.4.3. Downgrading to pushy 0.5.1 solves the issue.