> We must be sure that always_refresh=True don't break the lock.
>
No good. Can't get lock at all.
$ bin/withlist test
Loading list [EMAIL PROTECTED] (unlocked)
The variable 'm' is the test MailList instance
>>> m.Lock()
>>> m.Locked()
False
>>> m.Save()
Traceback (most recent call last):
Barry Warsaw wrote:
> Hi Tokio,
>
> I wonder if we shouldn't just be adding always_refresh=True to the
> mappers? I can't get to the SQLAlchemy site atm to provide a reference.
I can't access the sqlalchemy site either now. But, I tested my code
with two terminals using bin/withlist seeing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 27, 2007, at 4:22 AM, Tokio Kikuchi wrote:
>>> testing 2.2 code on my PC. What is curious about the LMTP/HTTP
>>> interfaces with SQLAlchemy based database is that changes
>>> commited in
>>> LMTP/HTTP sessions cannot be reflected on the oth
Barry Warsaw wrote:
> On Mar 27, 2007, at 4:22 AM, Tokio Kikuchi wrote:
>
>> I've submitted a patch to address this problem on SF patch area
>> because I'm not confident whether to check this in the svn. I hope
>> you have time to review and write a better patch.
>
> Hi Tokio,
>
> Thanks..
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 27, 2007, at 4:22 AM, Tokio Kikuchi wrote:
> I've submitted a patch to address this problem on SF patch area
> because I'm not confident whether to check this in the svn. I hope
> you have time to review and write a better patch.
Hi Tokio
Hi again,
Barry Warsaw wrote:
>> testing 2.2 code on my PC. What is curious about the LMTP/HTTP
>> interfaces with SQLAlchemy based database is that changes commited in
>> LMTP/HTTP sessions cannot be reflected on the other sessions. If I
>> subscribe an address via HTTP then it cannot be unsub
Barry,
>> Other than that, I think I've checked with i18n plain text message
>> deliveries for both regular and digest. Still to go are mime
>> multipart
>> messages and archives.
>>
>> I've also added a comment on Testing Mailman 2.2 wiki page how to test
>> run the 2.2 code.
>
> Thanks, and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 3, 2007, at 1:13 AM, Tokio Kikuchi wrote:
> Hi Barry,
Hi Tokio,
Man, I don't know what happened but I just got /plastered/ with email
this week. Between that and work, I haven't even touched the code. :/
> Since we at Japanese universitie
