On 11/12/05, Jonathan LaCour <[EMAIL PROTECTED]> wrote: > That is, essentially, correct. This issue arises when using the flup > forking WSGI server. It seems that changes don't quite "stick" > properly. I will make a change to an object in one request, and it > won't seem to "stick" when I make the next request (like the object > is still in the cache in a separate pre-forked process). Its > seemingly random. Sometimes it happens, other times it doesn't!
I updated the ticket to reflect this as the current status. I've targetted it for 0.9, but this is certainly one of the fuzziest ones as far as how it's going to be resolved (and who'll do it). Kevin
