> > However, maybe it > > is possible to "fix" pyicqt to stop getting TypeError on "strange" > > input from server? > > I read today about this problems on ICQ servers. Usual clients like > Pidgin also has it: user can't get contact-list from server. PyICQt > uses server-side contact list and without it can't works in any case. > I think, checking for every packet from server it's bad idea. Of > course, possible fix this current traceback, but it was temporary > problem and may be it don't will repeats in future. And we don't knows > what will after next update on ICQ servers
I agree that attempt to support any sort of unexpected server behaviour is strange at least. However, i'm interested [as a programmer] how in this particular case TypeError could happen - that means, how invalid server input could change the type of 'snac' object at oscar.py:1970 This may indicate a bug somewhere. Btw, while we are on topic. The serious issue that makes it virtually impossible to move local users from icq to jabber+pyicqt, is that after initial registration in the transport, user gets his icq contact list (sometimes huge!) imported into jabber roster in numeric form (as [EMAIL PROTECTED]). Is there any possibility to automatically import nicknames of ICQ contacts (including russian nicknames)? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "py-transports" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/py-transports?hl=en -~----------~----~----~----~------~----~------~--~---
