Chris wrote:
> On Mar 4, 8:38 am, "Mike Walker" <[EMAIL PROTECTED]> wrote:
>>> If you run a python file, ie. just double clicking it the only
>>> argument you will have will be the filename of the script. If you
>>> create a shortcut to the script and in the target box add your
>>> arguments (if y
On Mar 4, 8:38 am, "Mike Walker" <[EMAIL PROTECTED]> wrote:
> > If you run a python file, ie. just double clicking it the only
> > argument you will have will be the filename of the script. If you
> > create a shortcut to the script and in the target box add your
> > arguments (if you have quotati
"Mark Tolonen" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
>
> From the command line, the 'ftype' and 'assoc' commands can be used
> view how an extension is handled:
>
> C:\>assoc .py
> .py=Python.File
>
> C:\>ftype Python.File
> Python.File="C:\Python25\python.exe" "%1" %
"Mike Walker" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
>
>> If you run a python file, ie. just double clicking it the only
>> argument you will have will be the filename of the script. If you
>> create a shortcut to the script and in the target box add your
>> arguments (if yo
> If you run a python file, ie. just double clicking it the only
> argument you will have will be the filename of the script. If you
> create a shortcut to the script and in the target box add your
> arguments (if you have quotation marks place them after not inside)
> you will see your arguments
On Mar 4, 7:12 am, "Mike Walker" <[EMAIL PROTECTED]> wrote:
> I am having some problems with command line arguments in Windows. The same
> code under Linux works fine.
>
> In Windows I only get one argument no matter how many arguments are passed
> on the comm
I am having some problems with command line arguments in Windows. The same
code under Linux works fine.
In Windows I only get one argument no matter how many arguments are passed
on the command line. I think there is some problem with the way the .py
files are associated causing this. I'm
