Yukihiro Matsumoto wrote:
> 
>...
> 
> I know the first release of Python had OO capability, but if he really
> designed Python to be OO from day one, there's no class-type (or
> object-instance) separation, which he has to suffer until Python 3000.

I think it is accurate to say that Python was always had OO but it was
not deeply OO in its handling of basic types. Guido made a design
mistake in separating classes and types. Python 2.2 (now in alpha) will
correct that design mistake.

We've had a pretty civil discussion so far so I'd like to extend it to
ask if Ruby adherents do or do not see Ruby's current threading model as
a fairly major potential issue for someone thinking of moving from
Python to Ruby? My understanding is that a single blocking network call
will halt all threads which might mean hanging a GUI for example.

I became a Python advocate because I don't like being forced to program
in Perl (which happens because Perl is dominant in the scripting space).
Ruby is the only other scripting language that I would *like* to do a
project in. But for my current projects the threading weaknesses seem
somewhat prohibitive. I can imagine many (most!) others where it
wouldn't be a problem though.

What do the threading issues mean in a web server embedding context? Is
there a way to have a persistent pool of independent interpreters?
-- 
Take a recipe. Leave a recipe.  
Python Cookbook!  http://www.ActiveState.com/pythoncookbook