RetroSearch Browse

Tue Jul 14 14:53:40 CEST 2015 · https://mail.python.org/pipermail/python-dev/2015-July/140722.html

On 2015-07-14, at 14:39 , Nick Coghlan <ncoghlan at gmail.com> wrote:

> On 14 July 2015 at 22:06, Dima Tisnek <dimaqq at gmail.com> wrote:
>> Thus the question, how far should Python go to detect possible
>> erroneous user behaviour?
>> 
>> Granted it is in tests only, but why not detect assrte, sasert, saster
>> and assrat?
> 
> Because "r" and "e" are right next to each other on a QWERTY keyboard
> (so it's an easy typo to make), and transposing them doesn't change
> the overall shape of the word (so it's a hard typo to detect).

> If you get the "a" or "t" out of position you change the shape of the
> word so typos involving those are easier to detect visually, while "s"
> and "e" are on different keyboard rows so typos at that point in the
> word are less likely in the first place.

"sasert" fits these rules though.

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2015-July/140722.html below:

[Python-Dev] How far to go with user-friendliness