This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: debuggable/profileable Python framework
Type: enhancement Stage: resolved
Components: macOS Versions: Python 2.7
process
Status: closed Resolution: wont fix
Dependencies: Superseder:
Assigned To: Nosy List: bob.ippolito, ronaldoussoren
Priority: normal Keywords:

Created on 2004-02-08 02:15 by bob.ippolito, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Messages (2)
msg61154 - (view) Author: Bob Ippolito (bob.ippolito) * (Python committer) Date: 2004-02-08 02:15
It's standard procedure for frameworks on OS 
X is to have multiple binaries in the same framework 
for tasks such as debugging and profiling.  The developer would set 
the DYLD_IMAGE_SUFFIX environment variable in order to choose 
the non-standard image at runtime when they needed it.

It would rock if this could make it into the build scripts (so it would 
happen in OS X 10.4). I believe 
the only way right now is to configure+build three separate 
frameworks and stuff them all into one framework by hand.
msg88093 - (view) Author: Ronald Oussoren (ronaldoussoren) * (Python committer) Date: 2009-05-19 19:37
This might be useful for profiling. Debugging information is already 
present in the default build of the framework.

A seperate binary for --with-pydebug won't be possible as AFAIK --with-
pydebug changes the ABI and hence having both in the same framework will 
cause problems for extensions.

I'm not planning to work on this, but would be willing to review a patch.
History
Date User Action Args
2022-04-11 14:56:02adminsetgithub: 39912
2010-01-17 19:17:14ronaldoussorensetstatus: open -> closed
resolution: wont fix
stage: resolved
2009-05-19 19:37:01ronaldoussorensetnosy: + ronaldoussoren
messages: + msg88093
2009-02-14 11:34:39ajaksu2setversions: + Python 2.7
2004-02-08 02:15:54bob.ippolitocreate