Mark Nenadov wrote:
> 
> ...
> 
> To the best of my knowledge Python was designed originally with OOP in mind (not
> as an add on). Also, I wouldn't consider it a hybrid language.

Python exposes the "self" argument as a parameter to the method. Many
people take that as evidence that OO was bolted on. Really it was done
this way merely to keep the amount of "syntax" in the language low.

Nevertheless, it is true that Ruby is more deeply and completely object
oriented. I was playing today with adding methods to individual integers
which was mentally gratifying if not especially useful.

It seemed to only work on "smaller" integers though...I don't know why
that was. 

Python is moving into a deeper OO direction but Ruby is already there.
To me that wouldn't be enough to offset Ruby's immaturity issues but if
I had different priorities I could see how it might.
-- 
Take a recipe. Leave a recipe.  
Python Cookbook!  http://www.ActiveState.com/pythoncookbook