"Compile time" checking?

[en.karpachov at ospaz.ru]

On Fri, 12 Aug 2005 22:25:07 -0700
Steve Jorgensen wrote:

> Since Python does not use manifest typing, there's not much you can do about
> this, but typeless languages like this are great if you're using a process
> that finds the errors the compiler would otherwise find.  I'm referring, of
> course, to Test Driven Development (TDD).
> 
> If you do TDD, you won't miss compile-time checking much.  In fact, the extra
> kruft that manifest typing requires is an annoying burden when doing TDD, so
> Python is a breath of fresh air in this regard.

What test should one implement to catch that kind of errors like in OP
example?

> On 10 Aug 2005 08:53:15 -0700, "Qopit" <russandheather at gmail.com> wrote:
> 
> >#----
> >def tester(a,b,c):
> >  print "bogus test function",a,b,c
> >tester(1,2,3)  #this runs fine
> >tester(1,2)    #this obviously causes a run-time TypeError exception
> >#----

-- 
jk