os.startfile: Why is there no arguments option?

2011-10-12 Thread Christian Wutte
Hello all, as stated in the docs [1] os.startfile relies on Win32 ShellExecute(). So maybe someone can explain it to me, why there is no support for program arguments. That's quite a pity since os.startfile is the easiest way for an elevated run (with 'runas' as option) and without arguments of

Re: os.startfile: Why is there no arguments option?

2011-10-12 Thread Thomas Rachel
Am 12.10.2011 10:22 schrieb Christian Wutte: Hello all, as stated in the docs [1] os.startfile relies on Win32 ShellExecute(). So maybe someone can explain it to me, why there is no support for program arguments. Because it is intended to start an arbitrary file of any type (.txt, .doc, ...)

Re: os.startfile: Why is there no arguments option?

2011-10-12 Thread Thomas Heller
Am 12.10.2011 10:22, schrieb Christian Wutte: Hello all, as stated in the docs [1] os.startfile relies on Win32 ShellExecute(). So maybe someone can explain it to me, why there is no support for program arguments. That's quite a pity since os.startfile is the easiest way for an elevated run

Re: os.startfile: Why is there no arguments option?

2011-10-12 Thread Christian Wutte
On Oct 12, 11:27 am, Thomas Rachel nutznetz-0c1b6768-bfa9-48d5- a470-7603bd3aa...@spamschutz.glglgl.de wrote: Am 12.10.2011 10:22 schrieb Christian Wutte: Hello all, as stated in the docs [1] os.startfile relies on Win32 ShellExecute(). So maybe someone can explain it to me, why there is

Re: os.startfile: Why is there no arguments option?

2011-10-12 Thread Christian Wutte
On Oct 12, 11:45 am, Thomas Heller thel...@ctypes.org wrote: It is trivial to call ShellExecute with ctypes. Yes, but it would be easier to use os.startfile() instead of ctypes.windll.shell32.ShellExecute(), not? Further one must for sure check the MSDN page for ShellExecute for the five