[Numpy-discussion] slow numpy.clip ?

[David Cournapeau]

Travis Oliphant wrote:
> David Cournapeau wrote:
>> en I went back to home, I started taking a close look a numpy/core C 
>> sources, with the help of the numpy ebook. The huge source files make it 
>> really difficult for me to follow some things: I was wondering if there 
>> is some rationale behind it, or if this is just a remain of old 
>> developments of numpy.
>>
>> The main problem I have with those huge files is that I am confused 
>> between the functions parts of the public API, the one for backward 
>> compatibility, etc... I wanted to extract the PyArray_TakeFom function 
>> to see where the time is spent, but this is quite difficult, because of 
>> various dependencies.
>>
>> My question is then: is there any plan to change this ? If not, is this 
>> for some reasons I don't see, or is this just because of lack of manpower ?
>>   
>
> I'm not sure what you mean by "this".   I have no plans to change the 
> infrastructure, but naturally suggestions are always welcome.   You just 
> have to understand and figure out the limitations of trying to expose a 
> C-API.
"this" was just about the big source files, and I was wondering if there 
was a rationale or not. Your previous email answered this: there is a 
rationale. I don't have much experience in pure C python modules, and if 
this is the standard python way of doing things, I guess there is no 
other easy way of doing things.

Thank you for your explanation,

David