as to the most likely causes of this error coming up? Could it be
something like an error happening where it is not explicitly in a try
block, or an error happening while I'm already in an except block, or
something like that?
Thanks,
--JMike
--
http://mail.python.org/mailman/listinfo/python-list
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
-a wooga
I get this output:
there are 4 args
arg: printargs.py
arg: booga
arg: -a
arg: wooga
But on Windows Vista, when I run that command, I get
there are 1 args
arg: printargs.py
What's up with that?
--JMike
--
http://mail.python.org/mailman/listinfo/python
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
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
to Python 2.5
everywhere.)
--JMike
--
http://mail.python.org/mailman/listinfo/python-list
, to
present the elements to the content handler in different order, but I
couldn't immediately find any examples of the parser being subclassed.
Thanks for any pointers!
--JMike
--
http://mail.python.org/mailman/listinfo/python-list
, that'd be great.)
--JMike
--
http://mail.python.org/mailman/listinfo/python-list
, but I hope it gives you
enough to work with to find your own solution.
HTH,
-- Paul
Whoa. Outstanding. Excellent. Thank you!
--JMike
--
http://mail.python.org/mailman/listinfo/python-list
