On 14/08/2006, at 1:42 AM, Jim Gallacher wrote:
Lets target this to be done for 3.3. We just need some agreement
that proposed names are okay, plus a consensus on how we go about
deprecating old names. Do we have an option now which if enabled
prohibits use of old names and outputs some sor
Graham Dumpleton wrote:
>
> On 14/08/2006, at 1:42 AM, Jim Gallacher wrote:
>>> Lets target this to be done for 3.3. We just need some agreement that
>>> proposed names are okay, plus a consensus on how we go about
>>> deprecating old names. Do we have an option now which if enabled
>>> prohibits
[ http://issues.apache.org/jira/browse/MODPYTHON-185?page=all ]
Work on MODPYTHON-185 started by Jim Gallacher.
> _psp.parsestring doesn't check for empty values
> ---
>
> Key: MODPYTHON-185
> URL: http://issues.apac
[ http://issues.apache.org/jira/browse/MODPYTHON-185?page=all ]
Jim Gallacher reassigned MODPYTHON-185:
---
Assignee: Jim Gallacher
> _psp.parsestring doesn't check for empty values
> ---
>
>
[ http://issues.apache.org/jira/browse/MODPYTHON-185?page=all ]
Jim Gallacher resolved MODPYTHON-185.
-
Fix Version/s: 3.3
Resolution: Fixed
> _psp.parsestring doesn't check for empty values
> ---
>
>
Jim,This are my results for the memory leak search in apache.table(). The table object creates a memory pool by using apr_pool_create_ex() and destroys the pool using apr_pool_destroy(). I added a line in MpTable_New() before "return (PyObject*)t" to destroy the pool and ran 1M iterations and I no
Alexis Marrero wrote:
> Jim,
>
> This are my results for the memory leak search in apache.table().
>
> The table object creates a memory pool by using apr_pool_create_ex() and
> destroys the pool using apr_pool_destroy(). I added a line in
> MpTable_New() before "return (PyObject*)t" to destroy t
