pyprocessing/multiprocessing for x64?

[pigmartian]

I recently learned (from I response on this newsgroup to an earlier
query) of the processing module for working with subprocesses in a
similar manner to threading. For what I needed to do, it worked great
--- until I tried to run my code on an x64 box, for which that module
isn't available*. So, I'm just wondering if when processing is renamed
to multiprocessing and included in the standard lib for 2.6, will x64 be
supported?
~Scott

*yes, yes, I know. download the source and compile it myself.

[Christian Heimes]

Benjamin Kaplan wrote:

I'm not an expert on this, but I think that anything written for x86 (32
bit) machines can run on x64 machines.

Become an export - say the opposite :)

[Christian Heimes]

Benjamin Kaplan wrote:

I don't have a 64-bit machine, so I can only go off of what I read. This is
from the AMD64 FAQ<http://www.amd.com/us-en/Processors/ProductInformation/0,,30_118_9331_13278,00.html#100144>

Welcome to the world of marketing. The FAQ just explains that AMD64
compatible processors can still run 32bit programs. It doesn't say that
you can recompile your code for 64bit w/o trouble.

It's possible to write software that compiles and works on all sorts of
platforms and CPU architectures like X86, AMD64, IA64, PPC etc. The
Python interpreter is a good example.

However one can easily write C code that runs on 32bit X86 CPUs but
crashes on 64bit systems. The same code may run on a 64bit Linux/BSD
system but crashes on a Win32 X64 because 64bit Windows defines a long
as a 32bit datatype, while a long on 64bit Unix systems has 64bits.

Christian

[Christian Heimes]

Benjamin Kaplan wrote:

I don't have a 64-bit machine, so I can only go off of what I read. This is
from the AMD64 FAQ<http://www.amd.com/us-en/Processors/ProductInformation/0,,30_118_9331_13278,00.html#100144>

Welcome to the world of marketing. The FAQ just explains that AMD64
compatible processors can still run 32bit programs. It doesn't say that
you can recompile your code for 64bit w/o trouble.

It's possible to write software that compiles and works on all sorts of
platforms and CPU architectures like X86, AMD64, IA64, PPC etc. The
Python interpreter is a good example.

However one can easily write C code that runs on 32bit X86 CPUs but
crashes on 64bit systems. The same code may run on a 64bit Linux/BSD
system but crashes on a Win32 X64 because 64bit Windows defines a long
as a 32bit datatype, while a long on 64bit Unix systems has 64bits.

Christian

[pigmartian]

Interesting, I see Christian's responses to Benjamin, but not Benjamin's
posts themselves.

Anyways, the question remains: will multiprocessing be supported for the
x64 platform when it's released in 2.6?

pigmartian wrote:

I recently learned (from I response on this newsgroup to an earlier
query) of the processing module for working with subprocesses in a
similar manner to threading. For what I needed to do, it worked great
--- until I tried to run my code on an x64 box, for which that module
isn't available*. So, I'm just wondering if when processing is renamed
to multiprocessing and included in the standard lib for 2.6, will x64 be
supported?
~Scott

*yes, yes, I know. download the source and compile it myself.

[Kris Kennaway]

Benjamin Kaplan wrote:

The only problem I can see is that 32-bit programs can't access 64-bit
dlls, so the OP might have to install the 32-bit version of Python for
it to work.

Anyway, all of this is beside the point, because the multiprocessing
module works fine on amd64 systems.

Kris