Can't see the arguements when use Python in WSH.

GaryLee garywlee at gmail.com
Mon Sep 17 02:04:37 EDT 2007


On 9 16 ,   9 09 , Duncan Booth <duncan.bo... at invalid.invalid> wrote:
> GaryLee <garyw... at gmail.com> wrote:
> > Does anyone have the same situation? Is it my pywin32 package
> > corrupted? I've downloaded the last pywin32 package and executed the
> > site-packages\win32comext\axscript\client\pyscript.py to register the
> > PyScript. But, the problem is still there.
>
> I've no idea why pyscript.py doesn't set up the registry correctly, but it
> should all work if you run the command:
>
>    ftype pysFile=%SystemRoot%\System32\WScript.exe "%1" %*
>
> (If you wish you can try "ftype pysFile" first to see the current setting.
> On my system the file association wasn't set at all but it sounds like on
> yours it may be set but missing the %*)

I am sure that my setting in registry is correct. After run ftype
pysFile, I got the following response.

    > ftype pysFile
    pysFile=%SystemRoot%\System32\WScript.exe "%1" %*

I've also checked the DropHandler setting in registry. The value is
correct.
I just don't want to re-install my python 2.4, because I've installed
too many package.




More information about the Python-list mailing list