Why is Python a good first scripting language?

[Cameron Laird]

In article <mailman.1035069924.28648.python-list at python.org>,
Tim Peters  <tim.one at comcast.net> wrote:
>[Tim Teebken]
>> ...
>> So what it comes down to is, what is it about Python that would
>> make it the best place to start, when you only have time to learn one
>> scripting language?  Using the criteria above, what makes Python
>> preferable to its nearest competitors?
>
>Well, the criteria above themselves.  Grab an interpreter (it's free), fire
>up an interactive Python shell, and start playing with the tutorial of your
>choice (also free).  That's the fastest way to get answers to your questions
>you'll believe.  You'll like the answer you discover -- unless you're an
>idiot <wink>.
>
>that's-always-a-potential-problem-with-tims-ly y'rs  - tim
>
>

It might be hard to see the Python content in Tim's advice.
Here it is:  the grab-fire up-play process is remarkably 
quick and rewarding when Python is the subject.  While one
can imagine, say, Java advocates urging the same, their
installations *never* go as cleanly, non-computer people
don't feel comfortable with their language in the first
hour, and so on.
-- 

Cameron Laird <Cameron at Lairds.com>
Business:  http://www.Phaseit.net
Personal:  http://phaseit.net/claird/home.html