I'd also say let's prefer to support newer versions, but I don't know
how many people run the old version of twisted.
Maybe there should also be communication / co-operation with the twisted
team, so that new releases won't break the transports anymore.
Or the transports should state more clearly with which Twisted version
they work (like a dependency in package managers).
--
Andreas [ http://unstable.nl | xmpp:[EMAIL PROTECTED] ]
[ callto:ils.seconix.com/[EMAIL PROTECTED] ]
From [EMAIL PROTECTED] Mon Nov 14 16:00:40 2005
From: [EMAIL PROTECTED] (Daniel Henninger)
Date: Mon Nov 14 16:00:47 2005
Subject: [py-transports] Twisted 0.3.0 support
Message-ID: <[EMAIL PROTECTED]>
This is sort of for James's benefit, but I thought I would throw it
out to the list. The change that occured that caused PyAIM to fail
with 0.3.0 ended up being that the send function no longer accepts an
Element. It's expecting that you will hand it a string. I've been
toying with overriding send anyway because I need to do so for
Jabberd2's component protocol (well, I think I haven't worked that
functionality out yet). So PyTransport need a:
def send(self, obj):
if type(obj) == Element:
obj = obj.toXml()
component.Service.send(self,obj)
That does the trick. I'll be submitting the changes momentarily.
I'm going to pose this change on the twisted jabber list and see what
is said.
Daniel
--
"The most addictive drug in the world is music."
- The Lost Boyz
