On Jul 10, 2009, at 3:01 AM, Dag Sverre Seljebotn wrote:
> Robert Bradshaw wrote:
>> On Jul 9, 2009, at 3:36 AM, Robert Bradshaw wrote:
>>
>>> See http://trac.sagemath.org/sage_trac/ticket/5081 .
>>>
>>> sage: numpy.array([1, 10, 100]).dtype
>>> dtype('int64')
>>
>> Following up on this, I've als
Dag Sverre Seljebotn wrote:
> Robert Bradshaw wrote:
>> On Jul 9, 2009, at 3:36 AM, Robert Bradshaw wrote:
>>
>>> See http://trac.sagemath.org/sage_trac/ticket/5081 .
>>>
>>> sage: numpy.array([1, 10, 100]).dtype
>>> dtype('int64')
>>
>> Following up on this, I've also posted http://trac.sagemath.
Robert Bradshaw wrote:
> On Jul 9, 2009, at 3:36 AM, Robert Bradshaw wrote:
>
>> See http://trac.sagemath.org/sage_trac/ticket/5081 .
>>
>> sage: numpy.array([1, 10, 100]).dtype
>> dtype('int64')
>
> Following up on this, I've also posted http://trac.sagemath.org/
> sage_trac/ticket/6506 . This br
On Jul 9, 2009, at 3:36 AM, Robert Bradshaw wrote:
> See http://trac.sagemath.org/sage_trac/ticket/5081 .
>
> sage: numpy.array([1, 10, 100]).dtype
> dtype('int64')
Following up on this, I've also posted http://trac.sagemath.org/
sage_trac/ticket/6506 . This brings up an interface question, and
On Jul 7, 2009, at 6:32 PM, William Stein wrote:
>
> On Sun, Jul 5, 2009 at 3:15 AM, Dag Sverre
> Seljebotn wrote:
>>
>> Jason Grout wrote:
>>> Dag Sverre Seljebotn wrote:
1) I must be able to use NumPy together with the preparser (it's
just
too much hassle to turn it on and off,
On Sun, Jul 5, 2009 at 3:15 AM, Dag Sverre
Seljebotn wrote:
>
> Jason Grout wrote:
>> Dag Sverre Seljebotn wrote:
>>> 1) I must be able to use NumPy together with the preparser (it's just
>>> too much hassle to turn it on and off, and it kind of defeats the
>>> purpose.). That is, with the prepars
Jason Grout wrote:
> Dag Sverre Seljebotn wrote:
>> 1) I must be able to use NumPy together with the preparser (it's just
>> too much hassle to turn it on and off, and it kind of defeats the
>> purpose.). That is, with the preparser on, I should be able to run most
>> NumPy-using code without c
It's possible to dismiss the result of the survey because of the low
participation level, or to dismiss the results because of a hypothesis
that the respondents already KNOW Sage and want to know something
else.
But I suspect that there is also an underlying current of simple lack
of interest in
Dag Sverre Seljebotn wrote:
>
> 1) I must be able to use NumPy together with the preparser (it's just
> too much hassle to turn it on and off, and it kind of defeats the
> purpose.). That is, with the preparser on, I should be able to run most
> NumPy-using code without changes. (I don't think
Dag Sverre Seljebotn wrote:
> Robert Bradshaw wrote:
>> Currently the way to do numerics in Sage is to import scipy and numpy
>> (because they really have created a good stack), and turn off
>> preparsing (because those type issues get really annoying). At this
>> point, it may become unclea
10 matches
Mail list logo
