Re: Where do we stand on 3.2.2 final?

[Nicolas Lehuen]

As Jim wrote, the problem about the cache module has been fixed, but just so you know, it is a utility module which is used my the publisher in order to cache the published modules. It provides the automatic reload functionality in a thread-safe way. The problem was that it assumed threading was enabled in Pÿthon, which is not always the case.

Regards,
Nicolas

2005/10/21, Gregory (Grisha) Trubetskoy <[EMAIL PROTECTED]>:

On Fri, 21 Oct 2005, Jim Gallacher wrote:

> http://issues.apache.org/jira/browse/MODPYTHON-82 Unresolved

I guess this is another one of those where I wasn't paying attention, so
now I'm behind and don't really know what the cache module does... Too
much code to read too little time :)

Is the cache module something that we've decided is for 3.2 or is this a
3.3 future thing?

> http://issues.apache.org/jira/browse/MODPYTHON-83 Fixed in trunk

This looks like the right fix.

> Grisha was hoping for a release before ApacheCon US in December. If we need
> to do another beta we should get on it this coming week. Otherwise let's just
> get this thing out the door.

Let's may be kick around a little discussion of the cache module problem
and then see?

Grisha