On 1 Jun, 2010, at 13:25, Ronald Oussoren wrote:
>
> On 1 Jun, 2010, at 12:35, Michiel de Hoon wrote:
>
>> I tried this again on Mac OS X 10.5 and found that the Python inside
>> Python.app works as a framework, but python and pythonw do not:
>>
>> $
>> /Library/Frameworks/Python.framework/V
thon.app, so it doesn't interact appropriately with the window manager.
Python 2.6 uses execve in pythonw, so
/Library/Frameworks/Python.framework/Versions/2.7/Resources/Python.app/Contents/MacOS/Python
is the executable, and behaves as a framework.
--Michiel.
--- On Sun, 5/30/10, Ronald O
ack to execv on older versions of OSX).
What happens when you install Python using the beta installer at python.org?
Does that behave in the same way as the version you installed yourself?
I'm currently running 10.6, I'll try to find some time to test in a 10.5 VM
later this week. Coul
Thanks for your reply.
> import MacOS
> MacOS.WMAvailable()
> > False
>
> Which version of OSX are you on?
I see this behavior with both Mac OS X 10.4 and 10.5 (I don't have access to
10.6, so I haven't tried there).
Thanks,
--Michiel.
___
On 30 May, 2010, at 4:00, Michiel de Hoon wrote:
> Hi everybody,
>
> When I try to install Python as a framework:
>
> ./configure --enable-framework
> make
> make install
>
> then Python gets installed under
> /Library/Frameworks/Python.framework/Versions/2.7, but it doesn't seem to
> functi
Hi everybody,
When I try to install Python as a framework:
./configure --enable-framework
make
make install
then Python gets installed under
/Library/Frameworks/Python.framework/Versions/2.7, but it doesn't seem to
function as a framework:
>>> import MacOS
>>> MacOS.WMAvailable()
False
>>>
