give it a break. sure, we should be pythonic when we're programming at work and our code is likely to be maintained by others. but there's absolutely nothing wrong with pushing boundaries and learning by exploring and even - shock - getting things wrong.
you made some good points (particularly the fact that you lose dispatch by instance), but you don't need to keep jabbering away about the same points.
writing your own dialect of the language can be fun, but he is presenting his own style as 'pythonic' as opposed to the actual pythonic style built from functional composition - rather than method chaining.
I am banging on about a lot of the points because it seems very hard to explain to him that using clojure/arc/jquery styles is very very unpythonic.
you made some good points (particularly the fact that you lose dispatch by instance), but you don't need to keep jabbering away about the same points.