Eric Emsellem wrote:
> Hi Travis,
>
> sorry to bother you with that, but who's responsible with the numpy list?
> I am receiving ALL numpy-list emails directly now (although I always opted for
> the bundle option and checked that it is still on). I sent a mail about this,
> but no answer so far.
>
Hi Travis,
sorry to bother you with that, but who's responsible with the numpy list?
I am receiving ALL numpy-list emails directly now (although I always opted for
the bundle option and checked that it is still on). I sent a mail about this,
but no answer so far.
Anything wrong with the list? Som
nicholas cunliffe wrote:
> I think someone needs to sort out distribution lists, im getting lots
> of unstructured emails under many different titles
What exactly is the problem? If you mean that you used to get the digests rather
than the list emails themselves, this is an unfortunate side effect
Erin Sheldon wrote:
> Hi Travis -
>
> That is an impressive speed increase. Why is w/o dtype taking
> so much longer? Is this just from determining elements sizes and
> counts?
>
If you don't specify the data-type, then the auto-discovery algorithm
looks at each element in the nested sequence
On 11/16/06, Travis Oliphant <[EMAIL PROTECTED]> wrote:
> John Hunter wrote:
>
> >> "Erin" == Erin Sheldon <[EMAIL PROTECTED]> writes:
> >>
> >
> >
> >Erin> The question I have been asking myself is "what is the
> >Erin> advantage of such an approach?". It would be faster, but
I think someone needs to sort out distribution lists, im getting lots
of unstructured emails under many different titles
On 11/17/06, Francesc Altet <[EMAIL PROTECTED]> wrote:
> A Dijous 16 Novembre 2006 22:28, Erin Sheldon escrigué:
> > Hi Francesc -
> >
> > Unless I missed something, I think wha
John Hunter wrote:
>> "Erin" == Erin Sheldon <[EMAIL PROTECTED]> writes:
>>
>
>
>Erin> The question I have been asking myself is "what is the
>Erin> advantage of such an approach?". It would be faster, but by
>
> In the use case that prompted this message, the pull
Hi,
First of all, sorry that I've mixed t1, t2 and t3 in my previous
message (don't doing an overhaul before sending a message has
consequences :(). I'd try to clarify things here along introducing new
timings and other discoveries.
Then, as the message below is quite long, I will mention now my
Those preferences did not make it through. You
have to go back and re-check that preference.
Erin
On 11/17/06, Eric Emsellem <[EMAIL PROTECTED]> wrote:
> Hi,
> I am getting all the individual emails from the numpy discussion (and
> not the bundles), directly from their authors: something is wrong
Hi,
I am getting all the individual emails from the numpy discussion (and
not the bundles), directly from their authors: something is wrong with
the new list I think.
cheers
Eric
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://project
A Dijous 16 Novembre 2006 22:28, Erin Sheldon escrigué:
> Hi Francesc -
>
> Unless I missed something, I think what you have
> shown is that the combination of
> (getting data from database into python lists) +
> (converting to arrays)
> is what is taking time. I would guess the first
Hi Francesc -
Unless I missed something, I think what you have
shown is that the combination of
(getting data from database into python lists) +
(converting to arrays)
is what is taking time. I would guess the first takes
significantly longer than the second.
Erin
On 11/16/06, Fran
Hi,
Well, lets see whether this shiny new list works :)
El dj 16 de 11 del 2006 a les 11:05 -0700, en/na Tim Hochberg va
escriure:
> One weakness of this benchmark is that it doesn't break out how much of
> the sqlite3 overhead is inherent to the sqlite3 engine, which I expect
> is somewhat mor
13 matches
Mail list logo
