Python 2.7 interpreter can't connect to older interpreters

[Andrew Wilkins]

[remote] Traceback (most recent call last):
[remote] File "<string>", line 1, in ?
[remote] File "<string>", line 27, in ?
[remote] File "/home/andrew/prog/pushy/before/unittest/../pushy/client.py", line 29, in <module>
[remote] import __builtin__
[remote] ImportError: cannot import name __builtin__

[Andrew Wilkins (axwalk)]

There was a pretty dumb assumption in pushy/client.py, that .pyc contents would be useable in older interpreters. This previously held true so long as no Python 2.5/2.6 features were used. Something appears to have changed in 2.7 that makes the .pyc files unuseable by prior versions.

I think I will have to change pushy/client.py to always transmit the source. This may have a minor impact on the speed up connection creation.

[Eirikur Hallgrimsson (eirikur-h)]

Hi, I'm hitting something similar to this bug. Running on Python 2.7.3, I can use pushy with servers running Python 2.4 just fine.
Python 2.3 seems to be a problem. I hit the exception on line 60 of message.py where it raises IOError "End of File."
Minor tweaks to this area didn't work :-) This happens during the connection process and before control returns to my program.
I expect that if I could get past this, things might just work. Trying to pad the data to reach the required 21 characters didn't help.

Pushy 0.5.1 is what I'm running. Should I try the latest in version control?

[Andrew Wilkins (axwalk)]

Hi Eirikur. Seems I never mentioned it in the docs properly, but unfortunately Pushy requires Python 2.4 or greater (excluding the 3.x series). I can't recall the particulars of why this is the case.