[issue10666] OS X installer variants have confusing readline differences

Ned Deily added the comment: As of Python 3.3.0 and 2.7.9, the 32-bit-only OS X installers on python.org now have a minimum deployment target of 10.5, rather than 10.3. This means that all current OS X installers on python.org are now dynamically linked with the Apple-provided system editline

[issue10666] OS X installer variants have confusing readline differences

Ronald Oussoren added the comment: Download link for the latest version: http://opensource.apple.com/tarballs/libedit/libedit-31.tar.gz The archive only includes an Xcode based build system, the makefile based system was removed some time ago. It might be better to use

[issue10666] OS X installer variants have confusing readline differences

Ronald Oussoren added the comment: FWIW I'm in favor of shipping libedit as well with the 32-bit variant of the installer. The installer for 10.6 can continue to use the system install, that's good enough for to be used. The download link for the copy in OSX 10.6.7 is

[issue10666] OS X installer variants have confusing readline differences

Martin v. Löwis added the comment: It's true that we should try to avoid distributing GPL'ed code with binary installers. At a minimum, we would have to provide the source of readline for download also, and we would have to warn anybody redistributing our binaries that they must include the s

[issue10666] OS X installer variants have confusing readline differences

Ned Deily added the comment: ́Éric, Martin was involved in the earlier discussions when the support for editline was originally added to the readline module. We've been over this ground before. See Issue6872 and Issue6877. There are a number of options here. I plan to investigate the suppl

[issue10666] OS X installer variants have confusing readline differences

Éric Araujo added the comment: > Even if used a different file name, you still have to set up two > different sets of directives. I was assuming this would not be a problem: the .inputrc (or hypothetical .editrc file) is written once for all applications, it’s not a Python-specific task. Wha

[issue10666] OS X installer variants have confusing readline differences

Ned Deily added the comment: Even if used a different file name, you still have to set up two different sets of directives. The main drawback to the trivial suggestion is that it continues to pull in GNU readline, which is now GPLv3-licensed, into the python.org OS X installers. In general,

[issue10666] OS X installer variants have confusing readline differences

Éric Araujo added the comment: Ah, I thought that read_init_file used a different filename with libedit. Would there be a downside in implementing your suggestion labeled trivial, i.e. always use readline? -- ___ Python tracker

[issue10666] OS X installer variants have confusing readline differences

Ned Deily added the comment: Sorry, I don't see how that could help. The point I was making is that the directives accepted by GNU readline and BSD editline are completely different and one way or another the user is forced to deal with that. If you used read_init_file, you would still need

[issue10666] OS X installer variants have confusing readline differences

Éric Araujo added the comment: No. You wrote this: “Here's a snippet of what I have in my startup file: [code with if 'libedit' in readline.__doc__ complication] While obviously this can be handled, it seems like an unnecessary burden on users.” My message addresses this: using read_init_fi

[issue10666] OS X installer variants have confusing readline differences

Ned Deily added the comment: ́Éric, was your comment in msg135467 intended for another issue? -- ___ Python tracker ___ ___ Python-bu

[issue10666] OS X installer variants have confusing readline differences

Éric Araujo added the comment: FTR, readline.read_init_file() works with libedit too (provided that the config file uses libedit-style format), so you can remove the branch from your code. -- nosy: +eric.araujo ___ Python tracker

[issue10666] OS X installer variants have confusing readline differences

New submission from Ned Deily : 32-bit-only OS X installers build and link to a copy of the GNU readline library for use by the readline module in the standard library. But, the newer 64-bit/32-bit installer variants for 2.7 and 3.2 link to the OS X supplied BSD editline (libedit) library usi