Issue 995023: Should build Python dylib with -single_module

➜

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.

This issue has been migrated to GitHub: https://github.com/python/cpython/issues/40608

classification

Title:	Should build Python dylib with -single_module
Type:		Stage:
Components:	macOS	Versions:

process

Status:	closed	Resolution:	duplicate
Dependencies:		Superseder:
Assigned To:	jackjansen	Nosy List:	bob.ippolito, jackjansen
Priority:	normal	Keywords:

Created on 2004-07-21 06:27 by bob.ippolito, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Messages (1)
msg21734 - (view)	Author: Bob Ippolito (bob.ippolito) *	Date: 2004-07-21 06:27
According to bbum, dylibs built with -single_module load significantly faster. The default is not -single_module. A typical build of Python will have ~190 modules, when it could have just one. To check to see how many modules a dylib has, use otool - Mv on the dylib. Note that this is NOT for building extensions, only for building the dylib for Python itself.

msg21734 - (view)

Author: Bob Ippolito (bob.ippolito) * (Python committer)

Date: 2004-07-21 06:27

According to bbum, dylibs built with -single_module load 
significantly faster.  The default is not -single_module.  A typical 
build of Python will have ~190 modules, when it could have just 
one.  To check to see how many modules a dylib has, use otool -
Mv on the dylib.

Note that this is NOT for building extensions, only for building the 
dylib for Python itself.

History
Date	User	Action	Args
2022-04-11 14:56:05	admin	set	github: 40608
2004-07-21 06:27:01	bob.ippolito	create