On Wed, 05 Dec 2012, Yaroslav Halchenko wrote:
> On Wed, 05 Dec 2012, mark florisson wrote:
> > > Thanks, I merged it.
> > It'd be nice if you could add this as a testcase in the tests/run
> > directory as a "don't segfault" kind of test.
> I would be happy to extend the test battery but my bl
Yaroslav Halchenko, 10.12.2012 14:55:
> On Wed, 05 Dec 2012, Yaroslav Halchenko wrote:
>> On Wed, 05 Dec 2012, mark florisson wrote:
Thanks, I merged it.
>
>>> It'd be nice if you could add this as a testcase in the tests/run
>>> directory as a "don't segfault" kind of test.
>
>> I would be
On Mon, 10 Dec 2012, Stefan Behnel wrote:
> >> so how to make it 'effective'?
> > no hints from the experts? ;)
> Usually, running gc.collect() after this kind of test (i.e. as part of the
> doctest) is a good way to provoke a crash in time.
wasn't it obvious ? ;-) Thanks!
https://github.com
I've been noticing some unused function warnings of the following variety:
test.cpp:1189:12: warning: unused function
> '__pyx_pw_5numpy_7ndarray_1__getbuffer__' [-Wunused-function]
> static int __pyx_pw_5numpy_7ndarray_1__getbuffer__(PyObject *__pyx_v_self,
> Py_buffer *__pyx_v_info, int __pyx_v_
Thanks! Merged.
On Mon, Dec 10, 2012 at 12:08 PM, Bradley M. Froehle
wrote:
> I've been noticing some unused function warnings of the following variety:
>
>> test.cpp:1189:12: warning: unused function
>> '__pyx_pw_5numpy_7ndarray_1__getbuffer__' [-Wunused-function]
>> static int __pyx_pw_5numpy_7
