Author eric.araujo
Recipients eric.araujo, loewis, ned.deily, ronaldoussoren
Date 2011-05-09.17:43:48
SpamBayes Score 7.75925e-06
Marked as misclassified No
Message-id <1304963029.51.0.263393004655.issue10666@psf.upfronthosting.co.za>
In-reply-to
Content
> 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.  What I didn’t see is that users do not necessarily know about which file is used, so it’s at least a doc problem.

For the perceived problem with licensing, I’m adding Martin to nosy, not because he’s a PSF director but because he’s had to make similar choices for the Windows installers.

Martin, here’s the context: the Mac installer sometimes builds readline with the real readline or libedit.  There’s a doc problem which can be solved either by always using the same lib.  The easiest to implement now would be choosing readline, but Ned says: “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, we try to avoid shipping GPL-licensed software since it can complicate the allowable usages of the installed Python.”  Could you provide advice?
History
Date User Action Args
2011-05-09 17:43:49eric.araujosetrecipients: + eric.araujo, loewis, ronaldoussoren, ned.deily
2011-05-09 17:43:49eric.araujosetmessageid: <1304963029.51.0.263393004655.issue10666@psf.upfronthosting.co.za>
2011-05-09 17:43:48eric.araujolinkissue10666 messages
2011-05-09 17:43:48eric.araujocreate