2008/8/31 Alan G Isaac <[EMAIL PROTECTED]>:
> Thanks. So if I wish to determine the current
> state of documentation, is the right place to go:
> http://sd-2116.dedibox.fr/pydocweb/doc/ ?
Jarrod,
Could we set up a reverse proxy on doc.scipy.org to serve these pages
(until we move the app over to
On Sun, Aug 31, 2008 at 09:33, dmitrey <[EMAIL PROTECTED]> wrote:
> As for me I can't understand the general rule: when numpy funcs return
> copy and when reference?
It's driven by use cases and limitations of the particular functions.
> For example why x.fill() returns None (do inplace modificat
Thanks. So if I wish to determine the current
state of documentation, is the right place to go:
http://sd-2116.dedibox.fr/pydocweb/doc/ ?
Alan
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy
Sun, 31 Aug 2008 10:27:59 -0700, Robert Kern wrote:
> On Sun, Aug 31, 2008 at 09:26, Alan G Isaac <[EMAIL PROTECTED]> wrote:
>> I find this confusing:
>>
>> numpy.sort(a, axis=-1, kind='quicksort', order=None)
>>
>> Return copy of 'a' sorted along the given axis.
>>
>> Perform an inpla
On Sun, Aug 31, 2008 at 09:26, Alan G Isaac <[EMAIL PROTECTED]> wrote:
> I find this confusing:
>
> numpy.sort(a, axis=-1, kind='quicksort', order=None)
>
> Return copy of 'a' sorted along the given axis.
>
> Perform an inplace sort along the given axis using the algorithm
> specifi
As for me I can't understand the general rule: when numpy funcs return
copy and when reference?
For example why x.fill() returns None (do inplace modification) while
x.ravel(), x.flatten() returns copy? Why the latters don't do inplace
modification, as should be expected?
D.
Alan G Isaac wrot
I find this confusing:
numpy.sort(a, axis=-1, kind='quicksort', order=None)
Return copy of 'a' sorted along the given axis.
Perform an inplace sort along the given axis using the algorithm
specified by the kind keyword.
I suppose the last bit is supposed to refer to the ``so
