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 gregory.p.smith
Recipients Mark Harfouche, Robert Marshall, RomainGeissler1A, berker.peksag, donmez, emaste, eric.araujo, gregory.p.smith, koobs, martin.panter, ned.deily, ngie, ronaldoussoren
Date 2019-06-07.18:16:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1559931409.87.0.432367646637.issue13501@roundup.psfhosted.org>
In-reply-to
Content
In PR it you refer to -ledit and to editline.  libedit and libeditline appear to be two different libraries.

I was under the impression that libedit is the desirable one (it's what *BSD uses - coming originally from NetBSD if I understand correctly - which is how it wound up being macOS's choice).  I could also be wrong.

Is there a relationship between libedit and libeditline?  They both look like useful non-GPL readline alternatives.

We're building CPython internally at Google with libedit instead of readline of late and our initial patch to do this looks similar (though simpler) than your PR's readline.c changes.  The #ifdef __APPLE__ checks are replaced with a #ifdef HAVE_LIBEDIT check which we set in our pyconfig.h.

I'm interested in seeing this stuff get in one way or another, there's no reason we should tie people to GNU readline. :)
History
Date User Action Args
2019-06-07 18:16:50gregory.p.smithsetrecipients: + gregory.p.smith, ronaldoussoren, donmez, ned.deily, eric.araujo, ngie, berker.peksag, martin.panter, koobs, emaste, Mark Harfouche, RomainGeissler1A, Robert Marshall
2019-06-07 18:16:49gregory.p.smithsetmessageid: <1559931409.87.0.432367646637.issue13501@roundup.psfhosted.org>
2019-06-07 18:16:49gregory.p.smithlinkissue13501 messages
2019-06-07 18:16:49gregory.p.smithcreate