Python memory deallocate

[bruno at modulix]

Fredrik Lundh wrote:
> bruno at modulix" wrote:
> 
> 
>>*please* re-read carefully what I and Diez wrote earlier in this thread
>>before jumping to possibly erroneous conclusion. I didn't say that the
>>problem *actually* was with Python - just that it *may* have to do with
>>a memory management issue fixed in 2.5.
> 
> 
> the only thing that has changed is that Python 2.5 is slightly more likely to release
> memory areas held by the Python object allocator back to the C runtime memory
> allocator.  if you have a leak in your application, changing to Python 2.5 won't
> change a thing.

Which is mostly what I meant - sorry if it wasn't clear.

-- 
bruno desthuilliers
python -c "print '@'.join(['.'.join([w[::-1] for w in p.split('.')]) for
p in 'onurb at xiludom.gro'.split('@')])"