http://www.google.co.uk/search?q=site%3Abugzilla.redhat.com+...
http://www.google.co.uk/search?q=site%3Abugzilla.redhat.com+...
http://www.google.co.uk/search?q=site%3Abugzilla.redhat.com+...
(There are many more searches of this type you can do).
Red hat engineers suck (I know this isn't true)
I'm a genius (this isn't true either)
Different types of software have different needs and we shouldn't generalize about all software development based on our particular niche. Writing code that runs on other peoples systems is much harder than writing code that will run on servers I control. Python and ruby are great for the latter. I've never done the former at the scale of redhat. Writing code with a lot of collaborators is harder than writing it with a few collaborators.
What language do you prefer for your type of work?
also - there are code parsers like pylint that help you sanity check your source code in that manner.
speed - python is slow. We use python in scientific computing in extremely CPU intensive problems because python makes it very easy to control C and C++ layers that do the underlying work. that power in an interactive environment, complete with good visualization tools is great for science
If I typo something in ruby, I will not know unless that code path gets executed through a test. This would never happen in a statically typed language.
However I think the productivity benefits of dynamic typing far outweighs this risk in my experience.