From: MHammond at skippinet.com.au (Mark Hammond)
Date: Sat, 8 May 1999 09:46:50 +1000
Subject: newbie: on winnt - Do I something wrong, or is there just nothing
References: <7gvedu$1cl$1@news.vossnet.de>
Message-ID: <7gvtus$ivc$1@m2.c2.telstra-mm.net.au>
Content-Length: 1625
X-UID: 1778                                                

Florian W. wrote in message <7gvedu$1cl$1 at news.vossnet.de>...
>Hello Python-people
>
>Now at the office, i have to use win-N(o)T. Specially the wsh
>But VBScript is an ugly language, i would like to use something like
>PythonScript. But I don't managed to let it work (win32all, Build 123) :-(

If you are using Python 1.5.2, you should try using win32all build 125 -
especially if you are trying to use debugging.

Otherwise, can you give me an idea of _how_ it fails?

(As an aside, I cant see the advantage of using Python in WSH - why not just
use Python itself - you can still use the WSH object model from standard
Python using COM - just use "win32com.client.Dispatch()" instead of
"wsh.CreateObject()"

>cscript debugTest.pys does just nothing - not even an error message

This is in the axdebug\test directory.  It is part of a larger test suite,
and isnt designed to use used stand-alone.  You should be looking in the
demo directory (and if you find it lacking, feel free to contribute more
samples :-)

>And why is PyCOMTest not part of the package ?

It is a test harness only.  Most people wont want it.  The sources are
delivered in the COM sources, and you are free to build them.  Ditto the VB
test harness - the VB project and sources are shipped, but not the binaries.

>Have I have to switch to perl ?
Why?  Because you cant make all my test harnesses run first time?  If you
are having trouble making "normal" things work I could sympathise, but I
can't see any specific problems here...  Do any of the WSH Python samples
work for you?  If not, can you provide specific details?

Thanks,

Mark.







