I''ve got python 2.4.2 with TwistedSumo-2005-11-06. When I run PyAim-t
I'm getting the following error:
[EMAIL PROTECTED] pyaim-t-0.7b]# ./PyAIMt
Traceback (most recent call last):
File "main.py", line 4, in ?
import exception
File "/opt/wildfire/pyaim-t-0.7b/src/exception.py", line 6, in ?
import debug
File "/opt/wildfire/pyaim-t-0.7b/src/debug.py", line 7, in ?
import utils
File "/opt/wildfire/pyaim-t-0.7b/src/utils.py", line 57, in ?
from twisted.xish.domish import Element
ImportError: No module named xish.domish
I'm a python neophyte, but from what I can tell it seems that domish is
located in twisted.words.xish rather than twisted.xish. I'm not sure if
the location of xish changed at some point in twisted or what is going
on... any pointers would be appreciated.
-Steve
From [EMAIL PROTECTED] Thu Feb 2 04:52:11 2006
From: [EMAIL PROTECTED] (Alexey Nezhdanov)
Date: Thu Feb 2 04:52:37 2006
Subject: [py-transports] delays in pyAIM-t and pyICQ-t
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
? ????????? ?? ??????? 02 ??????? 2006 04:28 Daniel Henninger ???????(a):
> For that matter, if I run PyAIM or PyICQ over a wireless connection
> at half signal strength on a different machine from where ejabberd is
> running, it still runs plenty fast.
>
> I don't understand what's going on..
I can give you access to transport port on the problem box. You will be
running pyAIM-t on your box so we will see if it's ejabberd or pyAIM-t
problem.
Though I suspect that it related somehow on on which box you have started
transport.
> Oh also:
> otp R10B-9 for erlang if that helps anything
>
> Daniel
>
> On Feb 1, 2006, at 8:19 PM, Chris Carlin wrote:
> > Have you ever tested under ejabberd? Odd things had been happening
> > since I made that switch...
> >
> > I'm on gentoo with the following versions:
> > dev-python/twisted-words-0.3.0 *
> > dev-python/twisted-2.1.0 *
> > dev-python/twisted-xish-0.1.0-r1 *
> > dev-python/twisted-web-0.5.0-r1 *
> > dev-python/twisted-conch-0.6.0 *
> > dev-lang/python-2.4.2 *
> >
> > ~Chris
> >
> > Daniel Henninger wrote:
> >> I can't imaging what that might be. And again, I haven't seen a
> >> single difference on my side. =/ I mean there's certainly a lot
> >> that changed between 0.6 and 0.7. Wish I could see what you all
> >> are seeing on my own server... =/ Chris, what version of Twiste
> >> and Python are you using?
> >>
> >> Daniel
> >>
> >> On Jan 31, 2006, at 5:51 AM, Chris Carlin wrote:
> >>> So I finally got around to switching from 0.6 to 0.7b and I
> >>> realize now that I wasn't seeing precisely the problems Alexey
> >>> was describing... but now I am!
> >>>
> >>> Again, this is with ejabberd, which seems to delay the
> >>> transport's initialization in a way that jabberd2 did not. I now
> >>> see that 0.7b delays messages in ways that 0.6 didn't, though I
> >>> have no personal experience between 0.7b's behavior in jabberd2
> >>> versus ejabberd. Ahhh, orthogonalities....
> >>>
> >>> Anyway, another observation: often my messages will be sped up
> >>> when a message is incoming. If I am seeing 20 second delay on
> >>> outgoing messages and the other person sends a message, they
> >>> will often receive one message immediately.
> >>>
> >>> I haven't a clue what this means. Could it be some sort of
> >>> buffering you're not thinking about? Maybe some buffering
> >>> feature of twisted that changed during the 0.6-0.7b upgrade?
> >>>
> >>> ~Chris
> >
> > _______________________________________________
> > py-transports mailing list
> > [email protected]
> > http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports
>
> _______________________________________________
> py-transports mailing list
> [email protected]
> http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports
--
Respectfully
Alexey Nezhdanov
