Part I: The Origins of Python - Guido van Rossum on Python's history,
the influence of the ABC language, and Python's original design goals.
http://www.artima.com/intv/python.html
Part II: Python's Design Goals - Guido van Rossum on how Python was
originally intended to "bridge the gap between the shell and C," and
how it eventually became used on large scale applications.
http://www.artima.com/intv/pyscale.html
Part III: Programming at Python Speed - Guido van Rossum on the source
of Python's famed programmer productivity and the joys of exploring
new territory with code.
http://www.artima.com/intv/speed.html
Part IV: Contracts in Python - Guido van Rossum on the nature of
contracts in a runtime typed programming language such as Python.
http://www.artima.com/intv/pycontract.html
Part V: Strong versus Weak Typing - Guido van Rossum on the robustness
of systems built with strongly and weakly typed languages, the value
of testing, and whether he'd fly on an all-Python plane.
http://www.artima.com/intv/strongweak.html
Part VI: Designing with the Python Community - Guido van Rossum on the
importance of pythonic API design, the value of experience and
community feedback in design decisions, and the process of deciding
how to evolve Python's standard library.
> Part V: Strong versus Weak Typing - Guido van Rossum on the robustness
> of systems built with strongly and weakly typed languages, the value
> of testing, and whether he'd fly on an all-Python plane.
>
> http://www.artima.com/intv/strongweak.html
I am finding it hard to believe that Guido does not consider strong-vs-
weak-typing and static-vs-dynamic-typing to be orthogonal axes.