Thanks for the answers; that was the problem exactly.
--JMike
Duncan Booth wrote:
> It sounds like the registry entry for running Python files is messed up.
> Can you go to a command line and see what the command 'ftype Python.File'
> displays? (Assuming that command lines and ftype still work
"Duncan Booth" <[EMAIL PROTECTED]> escribió en el mensaje
news:[EMAIL PROTECTED]
> It sounds like the registry entry for running Python files is messed up.
> Can you go to a command line and see what the command 'ftype Python.File'
> displays? (Assuming that command lines and ftype still work on V
[EMAIL PROTECTED] wrote:
> But on Windows Vista, when I run that command, I get
>
> there are 1 args
> arg: printargs.py
>
> What's up with that?
It sounds like the registry entry for running Python files is messed up.
Can you go to a command line and see what the command 'ftype Pyth
Some further information: perl seems to do the same thing (losing
arguments).
We think it may have something to do with file association.
Any ideas anyone?
--JMike
--
http://mail.python.org/mailman/listinfo/python-list
By the way, note that if I say (on Vista)
python printargs.py booga -a wooga
I get the desired output:
> there are 4 args
> arg: printargs.py
> arg: booga
> arg: -a
> arg: wooga
So the quesiton still stands, what's up with that?
Thanks,
--JMike
--
http://mail.pytho
So I write this sript called printargs.py:
--
#!/usr/local/bin/python
import sys
print 'there are %d args' % len(sys.argv)
for arg in sys.argv:
print 'arg: %s' % arg
--
and make it executable. On pretty much every platform I can get my
hands on, when I run
printargs.py booga -a
