The most annoying typo error...

[Marcus Alanen]

On 7 May 2003 22:42:07 -0700, Asun Friere <afriere at yahoo.co.uk> wrote:
>Now I know a lot of peeps are gonna say, 'Learn to type!', but this is
>an important enough a problem (to me), to justify an intepreter
>re-write.    The intepreter would only have to check to see if a
>variable 'Librarian' was defined and and before raising NameErrors and
>ImportErrors, check them against a heuristic, to see if its some close
>misspelling, then correct my spelling for me, or raise the Error as
>approriate.  I mean c'mon, it's not too much to ask, is it?  [emoticon
>omitted]

The issue is that Python is designed to be a _very_ dynamic language.
A lot of times, this is a _strength_, not a weakness. This dynamic
nature means [as far as I have understood it] that you can't change
the run-time interpreter proper to do something like you suggest.

Some kind of a "debug mode" to the interpreter is another matter, for
people who want to program in a "static" way. Pychecker tries to find
common errors, see http://pychecker.sourceforge.net/. I haven't used
it that much, though.

Marcus