On 25 Oct, 2009, at 23:27, Robin wrote:

> On Sun, Oct 25, 2009 at 10:15 PM, William Kyngesburye
> <wokl...@kyngchaos.com> 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.6 (which is a symlink to the executable in the framework)
>> *only* responds to the arch command.
> 
> Thanks - I see that behaviour too now I checked.
> 
>> So, it looks like you configuration is using the env variable method.  I
>> don't compile my own Python, so I don't know if there is a configuration
>> option to set this behavior.
> 
> I tried but I can't get the environment variable to have any effect on
> the self-built python.org version.

That's because Apple's pythonw is a completely different executable than the 
python.org one. 

I'm working on a replacement for pythonw in 2.7 and 3.2 that will allow you to 
use the arch command to select an architecture. That version also works with 
2.6, but I don't think I'll be able to sneak it into 2.6.5 because the new 
executable is not 100% backward compatible with the current one.

Ronald

Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
Pythonmac-SIG maillist  -  Pythonmac-SIG@python.org
http://mail.python.org/mailman/listinfo/pythonmac-sig

Reply via email to