On Wed, Dec 28, 2011 at 06:39, Jaidev Deshpande
wrote:
> Hi
>
> It is said that function calls are expensive. Does that mean one must
> use available methods instead?
For the most part, it usually doesn't matter enough to care about.
Whether you use the methods or the functions should be dominate
Hi Jaidev,
On Wed, Dec 28, 2011 at 12:09:45PM +0530, Jaidev Deshpande wrote:
> Eg. x is a NumPy array, and I need its transpose
> Should I use
> >>> x.T
> or
> >>> numpy.transpose(T) ?
If you are wondering for a timing reason, use IPython's '%timeit' magic
to figure out if it does make a di
Hi
It is said that function calls are expensive. Does that mean one must
use available methods instead?
Eg. x is a NumPy array, and I need its transpose
Should I use
>>> x.T
or
>>> numpy.transpose(T) ?
Does it matter which one I'm using ? If not, under what conditions
does it become import
On 1/8/07, Travis Oliphant <[EMAIL PROTECTED]> wrote:
> Alan G Isaac wrote:
>
> >On Mon, 8 Jan 2007, Sebastian Haase apparently wrote:
> >
> >
> >>Please explain again what the original decision was based
> >>on.
> >>
> >>
> >
> >I think the real questions are:
> >what do the numpy developers want
Alan G Isaac wrote:
>On Mon, 8 Jan 2007, Sebastian Haase apparently wrote:
>
>
>>Please explain again what the original decision was based
>>on.
>>
>>
>
>I think the real questions are:
>what do the numpy developers want in the future,
>and what is the right path from here to there?
>
>
On Mon, 8 Jan 2007, Sebastian Haase apparently wrote:
> Please explain again what the original decision was based
> on.
I think the real questions are:
what do the numpy developers want in the future,
and what is the right path from here to there?
> I remember that there was an effort at some
