Lin wrote:
>
>Ah, this makes sense. Thanks.. The main reason I'm trying 64-bit
>Python is that I want to write files bigger than 4GB. This should work
>on Windows x64, right? (i.e., are the pointers bona fide 64 bit?)
Those two questions are not related. Win32 (NTFS) has always been able to
Lin schrieb:
> Ah, this makes sense. Thanks.. The main reason I'm trying 64-bit
> Python is that I want to write files bigger than 4GB. This should work
> on Windows x64, right? (i.e., are the pointers bona fide 64 bit?)
You can create files with more than 4GB on a 32bit OS, too. It depends
on
>
> > I installed the amd64 version of Python 2.6.1 on my Windows XP x64
> > system. I was expecting sys.maxint to be 9223372036854775807 (or 2 ^63
> > -1), but instead I got 2147483647 (i.e., 2^31-1) just like what I got
> > from a 32-bit version of Python. Is this by design or does it indicate
>
Lin schrieb:
> Hi,
>
> I installed the amd64 version of Python 2.6.1 on my Windows XP x64
> system. I was expecting sys.maxint to be 9223372036854775807 (or 2 ^63
> -1), but instead I got 2147483647 (i.e., 2^31-1) just like what I got
> from a 32-bit version of Python. Is this by design or does it
Hi,
I installed the amd64 version of Python 2.6.1 on my Windows XP x64
system. I was expecting sys.maxint to be 9223372036854775807 (or 2 ^63
-1), but instead I got 2147483647 (i.e., 2^31-1) just like what I got
from a 32-bit version of Python. Is this by design or does it indicate
a bug or an ins
