Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #55947
| From | Sherm Pendley <sherm.pendley@gmail.com> |
|---|---|
| Newsgroups | comp.lang.python |
| Subject | Re: Python 32-bit on Windows 64-bit |
| References | <mailman.111.1297449902.1633.python-list@python.org> <4D55A201.9060302@v.loewis.de> |
| Date | 2011-02-11 16:50 -0500 |
| Message-ID | <m262sqp7fk.fsf@sherm.shermpendley.com> (permalink) |
| Organization | X-Privat.Org NNTP Server - http://www.x-privat.org |
"Martin v. Loewis" <martin@v.loewis.de> writes:
> Am 11.02.2011 19:41, schrieb Craig Yoshida:
>> what kind of memory limitations to processes running on 32-bit python
>> (with 32-bit C extensions like scipy) have on 64-bit Windows? I'm
>> having occasional MemoryErrors when running a python program on
>> 64-bit Windows 7 that runs fine on my OS X machine. Both machines
>> are using a 64-bit OS and have 4GB of RAM.
>
> In addition to the limitations Michel reports: on a 32-bit system,
> objects are typically limited to using at most 2GiB, per object
> (of course, you could have at most two objects that come close to
> this size, since the whole address space would not be larger than
> 4GiB).
IIRC, 32-bit Windows programs are limited to 2GiB, reserving the rest
of the virtual address space for Windows' own use.
Also, 32-bit apps remain 32-bit, even if they're running on a 64-bit
capable OS. Assuming you're running Snow Leopard on your Mac, you're
using a 64-bit Python interpreter *and* a 64-bit OS. You need to have
both to take advantage of a 64-bit memory space.
sherm--
--
Sherm Pendley
<http://camelbones.sourceforge.net>
Cocoa Developer
Back to comp.lang.python | Previous | Next — Previous in thread | Find similar | Unroll thread
Re: Python 32-bit on Windows 64-bit "Martin v. Loewis" <martin@v.loewis.de> - 2011-02-11 21:54 +0100 Re: Python 32-bit on Windows 64-bit Sherm Pendley <sherm.pendley@gmail.com> - 2011-02-11 16:50 -0500
csiph-web