> 2009/10/26 Brent Pedersen :
> hi, i've seen this section:
> http://docs.scipy.org/numpy/Questions+Answers/#the-out-argument
>
> should _all_ functions with an optional out parameter have exactly that text?
> so if i find a docstring with reasonable, but different doc for out,
> should it be chang
hi, i've seen this section:
http://docs.scipy.org/numpy/Questions+Answers/#the-out-argument
should _all_ functions with an optional out parameter have exactly that text?
so if i find a docstring with reasonable, but different doc for out,
should it be changed
to that?
and if a docstring of a func
Technically, after "Needs Review," it's supposed to go through "Needs Work
(Reviewed)" The "by the book" way to do it would be to:
0 & 1) Provide comments in the Discussion section and change status to
"Needs Work (Reviewed)" (in either order);
2) Edit, if inclined.
3) Answer your own comments
When a documents status is "Needs Review" and when reviewing it we
feel it needs edits, should we add comments regarding the edits, or
should we feel free to edit it directly?
Chris
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail
On Sun, Oct 25, 2009 at 11:51 PM, Charles R Harris <
charlesr.har...@gmail.com> wrote:
>
>
> On Sun, Oct 25, 2009 at 4:21 PM, Ralf Gommers > wrote:
>
>> Hi all,
>>
>> Can anyone tell me if fftpack_lite is an exact C translation of the
>> fftpack Fortran code? Or at least close enough that the sig
On Sun, Oct 25, 2009 at 4:21 PM, Ralf Gommers
wrote:
> Hi all,
>
> Can anyone tell me if fftpack_lite is an exact C translation of the fftpack
> Fortran code? Or at least close enough that the signature, parameter
> descriptions and algorithm are the same?
>
> If so, I can use the fftpack Fortran
Hi all,
Can anyone tell me if fftpack_lite is an exact C translation of the fftpack
Fortran code? Or at least close enough that the signature, parameter
descriptions and algorithm are the same?
If so, I can use the fftpack Fortran sources (which have useful comments) to
write docs for fftpack_lit
Advanced Scientific Programming in Python
a Winter School by the G-Node and University of Warsaw
Scientists spend more and more time writing, maintaining, and
debugging software. While techniques for doing this efficiently have
evolved, only few scientists actually use them. As a result, instead
