On 2015-07-14, at 14:39 , Nick Coghlan <ncogh...@gmail.com> wrote: > On 14 July 2015 at 22:06, Dima Tisnek <dim...@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. _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
