Joe Berry schreef:
>>> home2>pkg_info | grep -i twist
>>> py24-twisted-1.3.0_2 An event-based Python framework for internet
>>> applications
>>> py24-twistedCore-2.4.0 An asynchronous networking framework for Python -
>>> Core modu
>> SASL doesn't work with Twisted 2.2+ yet. You'll need to either downgrade
>> Twisted or disable SASL.
>>
>
> Thanks for that information. I removed the saslUserName tag and pyaimt
> seemed to come up ok. Now I'm stuck at the next stage (I have
> successfully been running jabber 1.4.2 with AIM transport for a few years
> -- finally decided to upgrade -- I feel a little foolish with all these
> problems).
>
> I try and register the aim service using Exodus by referencing
> aim.topshot.com. I see the following debugging messages at the point
> where I do the registration:
Well, I think the thing really is that the transports haven't been
really tested with the new version of Twisted. They're known to work
with version 2.2 without SASL, but the recommended version really seems
to be 1.3 (2.0 also seems to work well).
Maybe you could try running the transports with Twisted 1.3?
From [EMAIL PROTECTED] Thu Aug 31 16:49:42 2006
From: [EMAIL PROTECTED] (Daniel Henninger)
Date: Thu Aug 31 16:48:53 2006
Subject: [py-transports] Install Problem w/pyaimt
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
On Aug 31, 2006, at 12:38 PM, Julius Schwartzenberg wrote:
> Joe Berry schreef:
>>>> home2>pkg_info | grep -i twist
>>>> py24-twisted-1.3.0_2 An event-based Python framework for internet
>>>> applications
>>>> py24-twistedCore-2.4.0 An asynchronous networking framework for
>>>> Python -
>>>> Core modu
>>> SASL doesn't work with Twisted 2.2+ yet. You'll need to either
>>> downgrade
>>> Twisted or disable SASL.
>>>
>> Thanks for that information. I removed the saslUserName tag and
>> pyaimt
>> seemed to come up ok. Now I'm stuck at the next stage (I have
>> successfully been running jabber 1.4.2 with AIM transport for a
>> few years
>> -- finally decided to upgrade -- I feel a little foolish with all
>> these
>> problems).
>> I try and register the aim service using Exodus by referencing
>> aim.topshot.com. I see the following debugging messages at the point
>> where I do the registration:
>
> Well, I think the thing really is that the transports haven't been
> really tested with the new version of Twisted. They're known to
> work with version 2.2 without SASL, but the recommended version
> really seems to be 1.3 (2.0 also seems to work well).
>
> Maybe you could try running the transports with Twisted 1.3?
Eww eww eww! Twisted 2.0! *cry* =) Twisted 2.0.1 is effectively
the minimum supported for PyAIMt/PyICQt becauses 2.0.0 had some nasty
bugs.
One other thing you might want to make sure you don't have enabled
is... useRouteWrap. That should not be turned on if SASL is turned
on for Jabberd2.
[One thing I wanted to do at some point is see if I can't get the
transports to detect what they've connected to.. like "oh hey, you
are jabberd2, i'm turning on this and that". Who knows how possible
that is ;D ]
Daniel
> _______________________________________________
> py-transports mailing list
> [email protected]
> http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports
