Re: Re: What problem are we trying to solve?

Serge Orlov wrote:

> I'd like to hear real stories when Python was rejected. I "sold"
> Python in 10 minutes two times when I worked for Transmeta and
> later for Infineon. The biggest worry was the lack of Python
> programmers which I debunked by turning an innocent man into a Python
> master
> in a matter of weeks :-)

Surely you've read the stories on c.l.p.  People are always asking for help
because their bosses won't let them use Python.

One reason I've kept the class keyword proposal seperate and only for
design-by-contract purposes is that we can reject the idea and still have
the fix for call_ and str_ if we want.  I personally think it does no harm
to include it and it will make people that appreciate design-by-contract
happy.

Just because we don't use design-by-contract doesn't mean others shouldn't.

If you don't like my class proposal, wait until you see my "type checking"
proposal.  It will be an assert just for types.  I think I'll propose it
now.