[SciPy-Dev] memory leak fftpack? (fixed)

[Matt Terry]

i'm working on it.  i have the dst/idst bindings working, and written
the documentation (including documenting the destroy_cache functions).
 i'm finishing up a test suite comparable to what dct has.  work is
bearing down on me right now, but hopefully have a complete pull
request in a week or so?

i wasn't going to make a destroy_all_cache() function.  i figure if
you know enough to want to kill the cache, you can probably read the
docs and see which cache you want killed.

-matt

On Sun, Dec 11, 2011 at 8:43 AM, Ralf Gommers
<ralf.gommers at googlemail.com> wrote:
>
>
> On Mon, Dec 5, 2011 at 8:13 PM, Bartosz Telenczuk
> <b.telenczuk at biologie.hu-berlin.de> wrote:
>>
>> Hi,
>>
>> > http://docs.scipy.org/doc/scipy/reference/fftpack.html shows the
>> > destroy_*fft*_cache() functions (though lacking any documentation).
>> > Would it be sufficient to update the docs to mention that the fftpack
>> > functions keep a cache and point you to the appropriate destroy
>> > function to nuke it?
>
>
> Matt, were you planning to do this while working on discrete sine
> transforms? If not, we should open a ticket for this.
>
> Ralf
>
>
>>
>>
>> Yes, that would be very helpful, indeed. Perhaps, it might be a good idea
>> to add a single function which cleans up all caches as well.
>>
>> It is worth alse mentioning that functions like signal.resample depend on
>> fftpack and they suffer from the same problem.
>>
>> Bartek
>> _______________________________________________
>> SciPy-Dev mailing list
>> SciPy-Dev at scipy.org
>> http://mail.scipy.org/mailman/listinfo/scipy-dev
>
>
>
> _______________________________________________
> SciPy-Dev mailing list
> SciPy-Dev at scipy.org
> http://mail.scipy.org/mailman/listinfo/scipy-dev
>