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 pitrou
Recipients belopolsky, cben, eric.araujo, ezio.melotti, flox, giampaolo.rodola, lesmana, loewis, mark.dickinson, ned.deily, pitrou, python-dev, r.david.murray, ronaldoussoren, serhiy.storchaka, steven.daprano, tshepang
Date 2013-05-06.13:24:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In-reply-to <>
> Now I don't know if I'm missing something painfully obvious, but
> having to bang out space-space-space-space for every indent is
> surely not going to be a win for usability ;-) Even if I am missing
> something, surely so will a lot of other users.

What *looks* painfully obvious to me is that Python doesn't force you
to use 4 spaces (or tabs) for indents :-)

> I use a readline completer that (in my opinion) does the Right Thing:
> at the start of the line, hitting TAB inserts a tab, otherwise it
> does completion. It also sets a history file, adds a couple of key
> bindings that I sometimes find useful, and wraps it all up in a
> class.

The "indent at beginning of line" thing sounds useful. The rest seems
to conflate the concept of a completer with the readline module itself.
Even though it's called rlcompleter, the rlcompleter module is
actually generic and could be used with other input schemes, so I don't
think it's the right place to set history options or key bindings.

In any case, you should post your patch as part of a separate issue, IMO.
Date User Action Args
2013-05-06 13:24:02pitrousetrecipients: + pitrou, loewis, ronaldoussoren, mark.dickinson, cben, belopolsky, giampaolo.rodola, ned.deily, ezio.melotti, eric.araujo, steven.daprano, r.david.murray, flox, lesmana, tshepang, python-dev, serhiy.storchaka
2013-05-06 13:24:02pitroulinkissue5845 messages
2013-05-06 13:24:02pitroucreate