[SciPy-Dev] Circular reference in interp1d causing memory errors

[Pauli Virtanen]

18.05.2013 14:14, josef.pktd at gmail.com kirjoitti:
[clip]
> Does anyone know a more explicit explanation?
> Or, is it really just the cyclical reference, even though it's a
> method (which always hold self)

Python gc is capable of breaking most reference cycles automatically.
The point however is that it does not run on every allocation. If you
allocate big objects that are kept around by a reference cycle at a too
rapid rate, you run into a memoryerror before the gc gets around to
breaking the cycles.

-- 
Pauli Virtanen