Command Line arguments

["Martin v. Löwis"]

Trent Mick wrote:
>>I used the python2.4.MSI from python.org site (dated 3-6-05). I think this
>>was the first time they went to MSI verses an exe based installer.
>>
>>it says Python 2.4 (#60 November 30th, 2004) when I start it.
> 
> 
> I think Martin has been doing MSIs for a little bit longer than that,
> but I'm not sure.

I started after 2.3, but MSIs were released for the 2.4 alpha and beta
releases, as well.

> Martin, is it possible that there is a bug in setting up the
> .py/Python.File association in the python2.4.msi? Here is the start of
> this thread:
> 
>     http://mail.python.org/pipermail/python-list/2005-August/296007.html

I don't think the 2.4 MSI has such a bug. There were various issues
in the alpha releases, but they got resolved. There was a bug in
the shortcuts (IDLE would not start if TARGETDIR had a space in it),
but that is an unrelated issue. Please refer to

http://www.python.org/2.4/bugs.html

for the most frequently reported bugs in 2.4.

> What association (if any) does your Python MSI setup?

"assoc .py" gives "Python.File", "ftype Python.File" gives
Python.File="C:\Python24\python.exe" "%1" %*

This is all done through registry (i.e. no advertised extensions).
Software\Classes\.py is Python.File,
Software\Classes\Python.File\shell\open\command is
"[TARGETDIR]python.exe" "%1" %*

My guess is that the MSI file was installed "Just for me",
and then a different user tries to find the associations,
which fails as they are in the other user's profile.

Alternatively, the "Register Extensions" feature in
the "Customize Python 2.4" dialog may have been
deselected.

Regards,
Martin