[Pythonmac-SIG] Numpy Scipy and Darwinports

2006-03-31 Thread Jaonary Rabarisoa
Hi all, I'd like to build numpy and scipy with the gcc 4.1 provided by darwinport (I fact, they need a fortran compiler). How can I do to change the compiler to be used with distutils ? I've tried something like this : python setup.py build --compiler=gcc-dp-4.1 ( all the file installed wi

[Pythonmac-SIG] Apple Remote "Mouse"

2006-03-31 Thread Johnston Jiaa
I recently bought a Macbook Pro from Apple.  As it comes with a remote, I thought it would be great to use it as a mouse when not in Front Row.  The fast forward button would move the cursor to the left, the volume increase would move it up the screen, etc and the play button would serve as a "clic

Re: [Pythonmac-SIG] Numpy Scipy and Darwinports

2006-03-31 Thread David M. Cooke
Jaonary Rabarisoa <[EMAIL PROTECTED]> writes: > Hi all, > I'd like to build numpy and scipy with the gcc 4.1 provided by > darwinport (I fact, they need a fortran compiler). How can I do to > change the compiler to be used with distutils ? I've tried something > like this : > > python setup.

Re: [Pythonmac-SIG] Numpy Scipy and Darwinports

2006-03-31 Thread Robert Kern
David M. Cooke wrote: > Jaonary Rabarisoa <[EMAIL PROTECTED]> writes: > > >>Hi all, >>I'd like to build numpy and scipy with the gcc 4.1 provided by >>darwinport (I fact, they need a fortran compiler). How can I do to >>change the compiler to be used with distutils ? I've tried something >>

Re: [Pythonmac-SIG] Wiki Formatting

2006-03-31 Thread Ronald Oussoren
On 31-mrt-2006, at 0:38, Christopher Barker wrote: > Ronald Oussoren wrote: >> I'd prefer not to have seperate Intel and PPC binaries. Would merging >> seperate >> Intel and PPC builds be of any use? > > Yes, though I'm not sure what you mean by merging. > > Do you mean lipo'ing them together? or

Re: [Pythonmac-SIG] PyObjC

2006-03-31 Thread Ronald Oussoren
On 31-mrt-2006, at 1:01, Dan Grassi wrote: > Hi, > > I had embedded python under 10.3.x but under 10.4 it fails on import > from Foundation import * > It seems that the problem is that it is launching the wrong python. > > sys.path: ['/System/Library/Frameworks/Python.framework/Versions/ > 2.3/l