Hi!
Daniel Henninger schrieb:
> I don't ever recommend using the SVN version unless you are ready todeal
> with potential problems and ideally report bugs. =) SVN isundergoing a
> lot of reworkings at the moment and is "not guaranteedto be stable".
Yeah I know. But the last stable release is really rusted ;-) and it
lacks some nice features.
And I hoped that the bugs were more hidden. I don't thought that an
obvious error like this would hide in this version.
Michael
From [EMAIL PROTECTED] Fri Feb 3 14:39:43 2006
From: [EMAIL PROTECTED] (Daniel Henninger)
Date: Fri Feb 3 14:39:52 2006
Subject: [py-transports] PyICQ-t subversion 03.02. - can't send messages
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
> Daniel Henninger schrieb:
>> I don't ever recommend using the SVN version unless you are ready
>> todeal with potential problems and ideally report bugs. =) SVN
>> isundergoing a lot of reworkings at the moment and is "not
>> guaranteedto be stable".
>
> Yeah I know. But the last stable release is really rusted ;-) and
> it lacks some nice features.
It sure is =D
> And I hoped that the bugs were more hidden. I don't thought that an
> obvious error like this would hide in this version.
I don't treat SVN as "should be able to function properly". I more
or less treat it as a version change tracker and a offsite copy of my
code. =)
When did you check out SVN btw, I never finished my thought
earlier . . . what actual release are you at? (svn release) r129
should have fixed the outgoing message thing. (and in fact I tested
it and it seems fine)
Daniel
>
> Michael
> _______________________________________________
> py-transports mailing list
> py-transports@blathersource.org
> http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports
>
>
