On Sun, Oct 25, 2009 at 10:15 PM, William Kyngesburye
wrote:
> Something I noticed with the Apple Python is that /usr/bin/python (which is
> it's own binary and not a symlink) *only* responds to the env variable
> VERSIONER_PYTHON_PREFER_32_BIT (I think that's the name). While
> /usr/bin/python2.
Something I noticed with the Apple Python is that /usr/bin/python
(which is it's own binary and not a symlink) *only* responds to the
env variable VERSIONER_PYTHON_PREFER_32_BIT (I think that's the
name). While /usr/bin/python2.6 (which is a symlink to the executable
in the framework) *onl
Hi,
I've been struggling with 32 vs 64 bit python on snow leopard. I built
an intel universal with:
./build-installer.py --sdk-path=/Developer/SDKs/MacOSX10.6.sdk/
--dep-target=10.6 --universal-archs=intel
It looks like it built correctly:
robin-mbp:bin robince$ file ./python2.6
./python2.6: Ma
On 24 Oct, 2009, at 15:23, Irmen de Jong wrote:
> Hamish Sanderson wrote:
>
>> Reading the docs. A few questions, if you don't mind:
>> - Will Pyro play well with PyObjC objects?
>
> I can't say anything about this, I have zero experience with PyObjC.
>
>> - How does it compare to, say, DO+Bon