On Oct 12, 11:45 am, Thomas Heller 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 parameters.
Then on e
On Oct 12, 11:27 am, Thomas Rachel 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 no support for
> > program arguments.
>
> Because it is inten
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 (with
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, ...)
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 lim