I want to impress the boss.

[Marty Backe]

You must have been reading a different post then me. I quote:

"I'm new to Python and am trying to get my company to adopt it as
a 'quick and dirty' glue tool."

Seems pretty clear to me that he's doesn't have much experience with
it. That doesn't mean he can't program in Python at some level, but
I'll stand by my position that he's probably not in the best position
to be advocating it's use.

COM was a follow on to his first statements. You actually read this as
being a post from an experienced Python user who was only new to COM?

Anyway, I didn't mean the post to be a flame (when I flame, there's no
doubt about it ;-) )

On Mon, 16 Oct 2000 09:10:20 -0400, Peter Hansen <peter at engcorp.com>
wrote:

<snip>

>As for the comment "when you can't even use it?", I would point out that
>the poster also does not imply that he can't use Python at all.  Perhaps
>you didn't really read the question, which was really asking about
>Python's COM support.  How many of us, even after using Python for
>months or years, can answer his question?  You?  Me?  I know I can't. 
>Couldn't you provide a helpful answer instead of a flame?
>
By "slowly mature", I didn't mean to take years. But months, yes.
There's no way you can begin using a new language and consequently be
in a position to advocate it's use in a matter a weeks. It takes time
to understand the various subtleties, strengths, weaknesses, etc.

I stand by my original post. But we can agree to disagree.

And for the sensitive among us, this post should not be taken as a
flame.

Thank you,

Marty

>Mike Fletcher's helpful answer demonstrated that (a) most people in this
>forum are willing to help, not criticize, (b) Python once again rules in
>easily acting as "glue", (c) there's probably no need to "slowly mature"
>with this language, since you can achieve great results (even in a mad
>rush) if you set yourself a challenging goal.  Python is not your
>father's scripting language.
>
>Our first project with Python involved using it to control two signal
>generators and a spectrum analyzer, and perform an "intermodulation
>test" on an amplifier module, with the results shown in a little Tk
>window.  This was in January.  If we'd "slowly matured" with Python we'd
>probably still be wasting time writing 4DOS scripts and little C
>utilities, rather than having all the fun we've had using Python for
>challenging and useful projects since then.  Instead, we convincingly
>demonstrated the utility of the language for non-trivial applications,
>and gained an unreasonable level of management support early on.  So
>there, too. :-)