[issue8868] Framework install does not behave as a framework

Ronald Oussoren added the comment: Thanks for testing. I've applied the patch (with some additional documentation) in r81649 (2.7) and r81650 (3.2). Other versions are not affected. -- resolution: -> fixed stage: needs patch -> committed/rejected status: open -> closed versions: +Py

[issue8868] Framework install does not behave as a framework

Michiel de Hoon added the comment: The patch solves the problem also on Mac OS X 10.5 (I tried 32-bits and 64-bits with the current python in trunk, after applying the patch). Thanks again! -- ___ Python tracker _

[issue8868] Framework install does not behave as a framework

Michiel de Hoon added the comment: The patch fixes the problem on Mac OS X 10.4. I'll try on 10.5 tomorrow. Thanks! -- ___ Python tracker ___

[issue8868] Framework install does not behave as a framework

Ronald Oussoren added the comment: Note that the subject is not entirely correct: the framework install is a framework install, but the python commandline doesn't behave like an application bundle. -- priority: normal -> high stage: -> needs patch ___

[issue8868] Framework install does not behave as a framework

Ronald Oussoren added the comment: The pythonw executable always uses execv on OSX 10.4 because posix_spawnv isn't available there. A possibly significant change is the value of argv[0] as passed to the Python.app executable. Could you check if this patch fixes the issue? Index: Mac/Tools/

[issue8868] Framework install does not behave as a framework

New submission from Michiel de Hoon : (The discussion for this bug started on the pythonmac-sig mailing list; see http://mail.python.org/pipermail/pythonmac-sig/2010-May/022362.html) When I try to install Python as a framework: ./configure --enable-framework make make install then Python gets