I haven't read through everything here, so this may be a duplicate entry. I just compiled 2.7.1 on my mac, os 10.6.5.
I did the following MACOSX_DEPLOYMENT_TARGET=10.6 ./configure --enable-framework make make install It all worked, and I have readline at the shell.(Which I think is provided by libedit.) Regarding readline v libedit, I think it's a licensing issue. Apple is leary of the GPL, and the BSD license, which governs libedit, is much more permissive. I dunno for sure though. That's just my reading of the situation. J On Tue, Nov 30, 2010 at 9:00 AM, David Dyck <[email protected]> wrote: > > On Mon, Nov 29, 2010 at 7:32 PM, Bradey Honsinger <[email protected]>wrote: > > > Were you asking about "readline" functionality? >> > http://docs.python.org/library/readline.html >> > http://www.google.com/search?q=+python+readline >> > >> >> I'm not at my Mac right now to check it out myself, but this looks >> like it might be related to this issue: >> >> http://bugs.python.org/issue6877 >> >> This was fixed in the trunk for 2.7 and backported to 2.6.5, so the >> behaviour you're seeing could be a regression, but take a look at your >> ./configure command line--there are a couple of command lines in this >> comment: >> >> http://bugs.python.org/issue6877#msg98858 >> >> None of them look directly related to readline, but >> MACOSX_DEPLOYMENT_TARGET=10.6 could have some effect. >> >> - Bradey >> > > coming from the linux side of things, I wasn't aware of the other libedit > family of BSD alternatives that are on the mac. > > eg. http://www.thrysoee.dk/editline/ > > Are there any background "stories" on why the divergence ( gnu-readline vs > libedit ) ? > > > >
