Case insensitivity

[Arthur]

>I've said it several times on this thread, already, and I'll keep repeating
it as long as you keep trying to >pretend you can't read, I guess: it's
_harder_ for a total beginner, who IS in any case having to confront many
>_INEVITABLE_ conceptual difficulties at the same time, and may be prone to
"blame themselves", with a loss of >self-confidence, for being unable to see
a good rationale for a certain behavior on the new tool's part. For
>somebody who's just a beginner at using specific module or package X, but
well knows from past general >experience that Python has this specific wart,
the wart entails a small loss of productivity; for a total >beginner the
impact can be worse, depending how much self-confidence they start with and
how much general ?>experience that, sigh, computers can and do behave
stupidly at times (because they're so programmed), just
>as doors are often mis-designed to require "push" vs "pull" instructions.

No, neither my reading or hearing is impaired - my typing is though more
than most.

>From the beginning I hoped the discussion, this Round, could be undertaken
without descending into an "I say this in respect to beginners experience"
and "you say that in respect to beginners experience".

I was all ears when you were talking about *you're* experience.

Among the problems:

If I disagree (which I do) what can I say other than:

"yeah well that's what *you* say".

Because I refuse to concede that you have any more insight into this
particular issue than I.  But you are Alex, so *I* end up sounding arrogant.
Does this guy think he's Alex?

But I am referencing the best hard evidence that the Python community has
managed to gather, and you are only offering one very smart guy's opinion.

Or else, in the end, its all just a matter of a definition of terms, and
what sounds like am argument in substance, is only a semantic argument.

So do let's stop.

Art