9:59 PM
To: Discussion of IronPython
Subject: Re: [IronPython] array.fromfile
Outstanding news! It worked. I finally had some extra time to change
the other two methods to match my modifications to CreateData and it
worked like a charm. Pretty cool. I think this is the best way to go,
so not too many
Outstanding news! It worked. I finally had some extra time to change
the other two methods to match my modifications to CreateData and it
worked like a charm. Pretty cool. I think this is the best way to go,
so not too many people get broken.
Thanks, JoeSox
On 2/24/07, Dino Viehland <[EMAIL PR
D] On Behalf Of Dino Viehland [EMAIL
PROTECTED]
Sent: Saturday, February 24, 2007 12:25 PM
To: Discussion of IronPython
Subject: Re: [IronPython] array.fromfile
Unfortunately there are several switch statements that will need to be updated.
They are in CreateData (generic type), ToStream (cast), Fr
TECTED] On Behalf Of JoeSox [EMAIL PROTECTED]
Sent: Saturday, February 24, 2007 11:30 AM
To: Discussion of IronPython
Subject: Re: [IronPython] array.fromfile
On 2/24/07, JoeSox <[EMAIL PROTECTED]> wrote:
> I really don't wish to modify the natural language processing tool
> module any
On 2/24/07, JoeSox <[EMAIL PROTECTED]> wrote:
> I really don't wish to modify the natural language processing tool
> module any more that I already have. Is it really necessary for
> IronPython to change the "minimum" sizes of the array types? (and
> hopefully this is my problem, I guess I will ne
On 2/24/07, J. Merrill <[EMAIL PROTECTED]> wrote:
> The file's size in bytes must be (at least) the number of values being read
> times the size of each value. If you are giving the file size in bytes as
> the length of the array, that will not work.
>
One of the challenges here is that this ex
At 04:14 PM 2/23/2007, JoeSox wrote (in part)
>On 2/23/07, Dino Viehland <[EMAIL PROTECTED]> wrote:
>> Is there an issue w/ switching to using the I type for the array instead of
>> the L type?
>
>I tried this but was unsuccessful. It still results in the same
>exception being thrown. If I am un
On 2/23/07, Dino Viehland <[EMAIL PROTECTED]> wrote:
> We're basically doing the same thing that the array.py is doing - the
> difference truly is just the item size. Python is implicitly doing the check
> by calling range(n) and doing the size check on each read. We're reading
> everything in
n a 32-bit platform
and 8 bytes on 64-bit but I don't have a 64-bit install of CPython).
From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of JoeSox [EMAIL PROTECTED]
Sent: Thursday, February 22, 2007 5:25 PM
To: Discussion of IronPython
Subject:
Ok, I found out that the length value of 260759 appears to be pulled
from a file that holds that value. So it is the same nomatter what
the environment is.
Now, here is the logic that my array.py file was using:
self.itemsize = self._descriptor[1] """I think _descriptor[1] =
typecode L, which in
Depending on how similar your array.py was to CPython's built-in array the
problem here may be that our long data type is 8 bytes instead of 4 like on
CPython. The documentation defines the "minimum" size and we use the native
sizes for the similar .NET types.
Try switching to using 'I' for th
Where did you get the value for the variable? How large is the file
(in bytes)? What is the encoding of the file? You might need to read the file
into a unicode string (assuming that you need some unicode characters) in order
to deal with the file's encoding.
I assume that fromfile's para
12 matches
Mail list logo
