On 4-Sep-09, at 11:59 PM, Charles R Harris wrote:
> The size of long depends on the compiler as well as the operating
> system. On linux x86_64, IIRC, it is 64 bits, on Windows64 I believe
> it is 32. Ints always seem to be 32 bits. But something funny is
> definitely going on. It shouldn't
On Sat, Sep 5, 2009 at 2:01 PM, Charles R
Harris wrote:
>
>
> On Fri, Sep 4, 2009 at 10:29 PM, Sturla Molden wrote:
>>
>> Charles R Harris skrev:
>> > The size of long depends on the compiler as well as the operating
>> > system. On linux x86_64, IIRC, it is 64 bits, on Windows64 I believe
>> > it
On Fri, Sep 4, 2009 at 10:29 PM, Sturla Molden wrote:
> Charles R Harris skrev:
> > The size of long depends on the compiler as well as the operating
> > system. On linux x86_64, IIRC, it is 64 bits, on Windows64 I believe
> > it is 32. Ints always seem to be 32 bits.
> If I remember the C standa
Charles R Harris skrev:
> The size of long depends on the compiler as well as the operating
> system. On linux x86_64, IIRC, it is 64 bits, on Windows64 I believe
> it is 32. Ints always seem to be 32 bits.
If I remember the C standard correctly, a long is guaranteed to be at
least 32 bits, wher
On Fri, Sep 4, 2009 at 9:22 PM, Sturla Molden wrote:
> David Warde-Farley skrev:
> >> The odd values might be from the format code in the error message:
> >>
> >>PyErr_Format(PyExc_ValueError,
> >>"%ld requested and %ld written",
> >>
David Warde-Farley skrev:
>> The odd values might be from the format code in the error message:
>>
>>PyErr_Format(PyExc_ValueError,
>>"%ld requested and %ld written",
>>(long) size, (long) n);
>>
>
> Yes, I saw that. My C is rusty
On Fri, Sep 4, 2009 at 3:54 PM, David Warde-Farley wrote:
> On 4-Sep-09, at 4:23 PM, Charles R Harris wrote:
>
> > The odd values might be from the format code in the error message:
> >
> >PyErr_Format(PyExc_ValueError,
> >"%ld requested and %ld written",
>
On 4-Sep-09, at 4:23 PM, Charles R Harris wrote:
> The odd values might be from the format code in the error message:
>
>PyErr_Format(PyExc_ValueError,
>"%ld requested and %ld written",
>(long) size, (long) n);
>
> The code that is im
On 4-Sep-09, at 5:01 PM, Charles R Harris wrote:
> Oh and is the Python python here 64 bits or 32 bits? What does
>
> file `which python`
>
> say?
I'm fairly sure it's a 64-bit python, but I don't have access to the
machine to check. I'll double check with the person who does.
David
__
On Fri, Sep 4, 2009 at 1:36 PM, David Warde-Farley wrote:
> A friend of mine is trying to save approx 2GB of float32s with
> np.save, and it's been failing. I traced it to PyArray_ToFile in core/
> src/convert.c:
>
> Traceback (most recent call last):
> File "preprocessTIMIT.py", line 302, in
>
On Fri, Sep 4, 2009 at 1:36 PM, David Warde-Farley wrote:
> A friend of mine is trying to save approx 2GB of float32s with
> np.save, and it's been failing. I traced it to PyArray_ToFile in core/
> src/convert.c:
>
> Traceback (most recent call last):
> File "preprocessTIMIT.py", line 302, in
>
On 4-Sep-09, at 3:36 PM, David Warde-Farley wrote:
> A friend of mine is trying to save approx 2GB of float32s with
> np.save, and it's been failing. I traced it to PyArray_ToFile in core/
> src/convert.c:
That should be core/src/multiarray/convert.c, sorry.
The system it's running on is:
A friend of mine is trying to save approx 2GB of float32s with
np.save, and it's been failing. I traced it to PyArray_ToFile in core/
src/convert.c:
Traceback (most recent call last):
File "preprocessTIMIT.py", line 302, in
main()
File "preprocessTIMIT.py", line 299, in main
nu
13 matches
Mail list logo
