On 2009-07-18, David Cournapeau wrote:
> On Fri, Jul 17, 2009 at 4:11 AM, Pauli Virtanen wrote:
[clip]
>> Yeah, currently there's no way to do that. I can probably add
>> numpy*function/cfunction/... etc. directives that allow this.
>>
>> An alternative is to use
>>
>> .. rubric:: Notes
>>
On Fri, Jul 17, 2009 at 4:11 AM, Pauli Virtanen wrote:
> On 2009-07-16, David Cournapeau wrote:
>> Hi Pauli,
>>
>> On Sat, Jul 4, 2009 at 9:59 PM, Pauli Virtanen wrote:
>>> Hi,
>>>
>>> When you add new functions to Numpy, please include
>>>
>>> .. versionadded:: 1.4.0
>>
>> What is the best way
On 2009-07-16, David Cournapeau wrote:
> Hi Pauli,
>
> On Sat, Jul 4, 2009 at 9:59 PM, Pauli Virtanen wrote:
>> Hi,
>>
>> When you add new functions to Numpy, please include
>>
>> .. versionadded:: 1.4.0
>
> What is the best way to do this in the reference guide directly as
> well (for C API).
Hi Pauli,
On Sat, Jul 4, 2009 at 9:59 PM, Pauli Virtanen wrote:
> Hi,
>
> When you add new functions to Numpy, please include
>
> .. versionadded:: 1.4.0
What is the best way to do this in the reference guide directly as
well (for C API). For example, I added the function npy_copysign for
1.4.
Hi,
When you add new functions to Numpy, please include
.. versionadded:: 1.4.0
in the Notes section of the function's docstring, and add the
functions to an appropriate section of the reference guide. Like
this:
http://projects.scipy.org/numpy/changeset/7107
This way, users can keep