On 8. mai 2011, at 17.32, Warren Weckesser wrote:
>
>
> On Sun, May 8, 2011 at 7:23 PM, Charles R Harris
> wrote:
>
>
> On Sun, May 8, 2011 at 3:15 PM, Paul Anton Letnes
> wrote:
> Hi,
>
> it seems that I have found a bug in numpy.ndarray. numpy 1.5.1, python 2.7.1
> from macports on ma
On Sun, May 8, 2011 at 7:23 PM, Charles R Harris
wrote:
>
>
> On Sun, May 8, 2011 at 3:15 PM, Paul Anton Letnes <
> paul.anton.let...@gmail.com> wrote:
>
>> Hi,
>>
>> it seems that I have found a bug in numpy.ndarray. numpy 1.5.1, python
>> 2.7.1 from macports on mac os x 10.6.7. I got the same er
On Sun, May 8, 2011 at 19:23, Charles R Harris
wrote:
>
> On Sun, May 8, 2011 at 3:15 PM, Paul Anton Letnes
> wrote:
>>
>> Hi,
>>
>> it seems that I have found a bug in numpy.ndarray. numpy 1.5.1, python
>> 2.7.1 from macports on mac os x 10.6.7. I got the same error on Fedora 14
>> with numpy 1.
On Sun, May 8, 2011 at 3:15 PM, Paul Anton Letnes <
paul.anton.let...@gmail.com> wrote:
> Hi,
>
> it seems that I have found a bug in numpy.ndarray. numpy 1.5.1, python
> 2.7.1 from macports on mac os x 10.6.7. I got the same error on Fedora 14
> with numpy 1.4.1 and python 2.7. Appending a [0] to
On Sun, May 8, 2011 at 2:45 PM, Keith Goodman wrote:
> I'm writing a function that accepts four possible dtypes: int32,
> int64, float32, float64. The function will call a C extension (wrapped
> in Cython). What are the equivalent C types? int, long, float, double,
> respectively? Will that work o
I want to add a question: is there a function that returns the name of the
corresponding C type given the numpy type?
On Sun, May 8, 2011 at 2:45 PM, Keith Goodman wrote:
> I'm writing a function that accepts four possible dtypes: int32,
> int64, float32, float64. The function will call a C exte
I'm writing a function that accepts four possible dtypes: int32,
int64, float32, float64. The function will call a C extension (wrapped
in Cython). What are the equivalent C types? int, long, float, double,
respectively? Will that work on all systems?
___
Hi,
it seems that I have found a bug in numpy.ndarray. numpy 1.5.1, python 2.7.1
from macports on mac os x 10.6.7. I got the same error on Fedora 14 with numpy
1.4.1 and python 2.7. Appending a [0] to the last line solves the problem.
% python testcrash.py
On Sun, May 8, 2011 at 11:42 AM, Skipper Seabold wrote:
> On Fri, May 6, 2011 at 11:30 AM, Till Stensitzki wrote:
>> Hi,
>> discovered another small bug. Windows 7 32 bit, Python 2.6.
>>
>> In [1]: np.__version__
>> Out[1]: '1.5.1'
>>
>> In [2]: a=np.zeros((0,2))
>>
>> In [3]: np.linalg.qr(a)
>>
On Fri, May 6, 2011 at 11:30 AM, Till Stensitzki wrote:
> Hi,
> discovered another small bug. Windows 7 32 bit, Python 2.6.
>
> In [1]: np.__version__
> Out[1]: '1.5.1'
>
> In [2]: a=np.zeros((0,2))
>
> In [3]: np.linalg.qr(a)
> ** On entry to DGEQRF parameter number 4 had an illegal value
>
In
===
EuroScipy 2011 - Deadline Extended!
===
Deadline extended!
You can submit your contribution until Friday May 13.
-
The 4th European meeting on Python in Science
11 matches
Mail list logo