On Oct 23, 2009, at 3:01 AM, Stefan Behnel wrote: > Dag Sverre Seljebotn wrote: >> let's get as many as possible to test with the refnanny turned on >> (and let's make it easy, say, let's include the code to stick in ones >> setup.py in the RC release notes). > > Would there be a way to enable that automatically for an alpha > release? I > know, this requires the external refnanny module, but wouldn't it be > possible to enable it by default, and then add a fallback dead-nanny > into > the generated code that would just ignore calls and would be used if > the > refnanny itself isn't found? That would eat some performance but would > allow users to enable the refnanny by simply having it lying around in > their PYTHONPATH, instead of requiring a separate build option.
I'm not so sure about the silent fallback, but +1 to enabling it for alphas (or even releasing an alpha and alpha-refnanny). > Although I admit that there should be enough of an incentive to > enable a > little option in your setup.py. It's never been so easy to make sure > that > some out-of-your-control generated code is memory leak free... You can add -DCYTHON_REFANNAY to your cflags, though that needs to be done extension by extension, so I agree there should be a better way. - Robert _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
