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.

Author ned.deily
Recipients l0nwlf, ned.deily, ronaldoussoren
Date 2010-04-11.07:09:35
SpamBayes Score 1.0658141e-14
Marked as misclassified No
Message-id <1270969777.97.0.820822320185.issue8365@psf.upfronthosting.co.za>
In-reply-to
Content
Issue6877 (and subsequent fixes in Issue8066) allows the Python readline module to be built and linked with the OS X editline (libedit) library rather than with the GNU readline library (which is not included with OS X).  However, the libedit included in versions of OS X prior to 10.5 is considered too broken to use here.

By default, if you do not specify an --with-universal-archs other than "32-bit" to configure or if you do not explicitly set MACOSX_DEPLOYMENT_TARGET to another value, configure defaults to using "10.4" (or earlier) so the building of the readline module is skipped.  You can check this:

>>> from distutils.sysconfig import get_config_var 
>>> get_config_var('MACOSX_DEPLOYMENT_TARGET')
'10.4'

(Whether this is the best default is another question.)

As it stands, to be able to build the readline module, either:

(1) supply the GNU readline library as a local library, or

(2) ensure you are building with a deployment target of at least 10.5.  For example:

    ./configure MACOSX_DEPLOYMENT_TARGET=10.6 ; make

Also note that option (2) is not available for 3.1.x since the changes to support editline/libedit were not ported to it; they are, however, in 2.6.5, 2.7 (trunk), and 3.2 (py3k).
History
Date User Action Args
2010-04-11 07:09:38ned.deilysetrecipients: + ned.deily, ronaldoussoren, l0nwlf
2010-04-11 07:09:37ned.deilysetmessageid: <1270969777.97.0.820822320185.issue8365@psf.upfronthosting.co.za>
2010-04-11 07:09:36ned.deilylinkissue8365 messages
2010-04-11 07:09:35ned.deilycreate