Summary of messages to the zope-tests list.
Period Tue Jan 29 12:00:00 2008 UTC to Wed Jan 30 12:00:00 2008 UTC.
There were 5 messages: 5 from Zope Unit Tests.
Tests passed OK
---
Subject: OK : Zope-2.7 Python-2.3.6 : Linux
From: Zope Unit Tests
Date: Tue Jan 29 20:51:43 EST 2008
URL
Hi everyone,
I have come across a situation, where temporarily the session data for a user
is not available.
Scenario: User 1 creates some session data. While a user 2 creates also some
session data, user 1's data is not accessible.
The problem plays out in two ways:
1. The data's __dict__ re
Stephan Richter wrote at 2008-1-30 08:45 -0500:
> ...
>1. The data's __dict__ returns an empty dictionary. When you access an
>attribute directly, though, the data can be seen. This symptom can be
>reliably reproduced.
This is normal for persistent objects.
When a persistent object is in Ghos
Leonardo Rochael wrote at 2008-1-27 22:29 -0800:
> ...
>Closing the NamedTemporaryFile after consuming it and before opening the
>blob makes the matters worse, since Windows removes the file from under Blob
>*after* it has been consumed, so we'll have to think of a different strategy
>for consuming
Hi,
It's been a long day and I am way out of my league on this issue, so I
will just go in off-topic mode and share a bash trick.
Stephan Richter, on 2008-01-30:
> cd sessionIssue2
> for number in 1 2 3 4 5 6 7 8 ;do sh sessionTest.sh;done
You can also do:
for number in $(seq 8); do sh sessio
