Author dabeaz
Recipients Martin Sekera, arigo, dabeaz, ezio.melotti, larry, martin.panter, pitrou, r.david.murray
Date 2015-07-09.09:43:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1436435008.81.0.0528676164816.issue23441@psf.upfronthosting.co.za>
In-reply-to
Content
Frivolity aside, I really wish this issue would get more traction and a fix.

Indentation is an important part of the Python language (obviously).  A pretty standard way to indent is to hit "tab" in whatever environment you're using to edit Python code.

Yet, at the interactive prompt, tab doesn't actually indent on a blank line. Instead, it autocompletes the builtins.  Aside from it being highly annoying (as previously mentioned), it is also an embarrassment.

Newcomers to Python will very often try things out using the stock interpreter before moving on to more sophisticated environments.  The fact that tab is broken from the get-go leaves a pretty sour impression when not even the most basic tutorial examples work at the interactive console (and keep in mind that whitespace sensitivity is probably already an issue on their minds).

Experienced Python users coming from Python 2 to Python 3 are going to find that tab is busted in Python 3.  Well, of course it's busted because everything is busted in Python 3.  "Wow, this really sucks as bad as everyone says" they'll say. 

So, with that as context, I'm really hoping I don't have to watch people use a busted tab key for another entire release cycle of Python 3 as I did for Python-3.4. 

I have no particular thoughts about the specifics (tabs vs. spaces) or the amount of indentation.   It's the autocomplete on empty line that's the issue.
History
Date User Action Args
2015-07-09 09:43:28dabeazsetrecipients: + dabeaz, arigo, pitrou, larry, ezio.melotti, r.david.murray, martin.panter, Martin Sekera
2015-07-09 09:43:28dabeazsetmessageid: <1436435008.81.0.0528676164816.issue23441@psf.upfronthosting.co.za>
2015-07-09 09:43:28dabeazlinkissue23441 messages
2015-07-09 09:43:27dabeazcreate