Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #44463
| Newsgroups | comp.lang.python |
|---|---|
| Date | 2013-04-27 22:06 -0700 |
| References | <2e11de8b-f7e1-407f-a2fd-a08d5ce55d0b@googlegroups.com> <pan.2013.04.28.03.53.25.536000@nowhere.com> |
| Message-ID | <d2c227b9-7536-4ab3-827a-b8953fca41ba@googlegroups.com> (permalink) |
| Subject | Re: "python.exe has stopped working" when os.execl() runs on Windows 7 |
| From | cormogram@gmail.com |
I did that but unfortunately the 'bug' persists. :(
I've chosen the os module because I though it would be more portable. :/
On Sunday, April 28, 2013 12:53:25 AM UTC-3, Nobody wrote:
> On Sat, 27 Apr 2013 17:22:31 -0700, cormogram wrote:
>
>
>
> > Was trying os.execl() and got a "python.exe has stopped working" on my
>
> > Windows 7 Ultimate SP1 x64 desktop.
>
> >
>
> > I'm using Python 2.7.4 and that happens when the second arg is ''. For
>
> > example:
>
> >
>
> > os.execl('filename.exe','')
>
>
>
> Note that, by convention, the second argument should normally also be the
>
> filename (the second argument will be available to the program as
>
> argv[0]), e.g.:
>
>
>
> os.execl('filename.exe','filename.exe')
>
>
>
> If successful, the exec* functions don't return. On Unix, the new program
>
> replaces the existing program in the current process. IIRC, the Windows
>
> version executes the program in a child process then exit()s upon
>
> completion.
>
>
>
> The exec* functions probably shouldn't be used within a program which uses
>
> any of the more complex OS features (e.g. GUI), as they will block event
>
> processing, background threads, etc.
Back to comp.lang.python | Previous | Next — Previous in thread | Find similar | Unroll thread
"python.exe has stopped working" when os.execl() runs on Windows 7 cormogram@gmail.com - 2013-04-27 17:22 -0700
Re: "python.exe has stopped working" when os.execl() runs on Windows 7 Dave Angel <davea@davea.name> - 2013-04-27 20:55 -0400
Re: "python.exe has stopped working" when os.execl() runs on Windows 7 cormogram@gmail.com - 2013-04-27 18:05 -0700
Re: "python.exe has stopped working" when os.execl() runs on Windows 7 Dave Angel <davea@davea.name> - 2013-04-27 22:02 -0400
Re: "python.exe has stopped working" when os.execl() runs on Windows 7 cormogram@gmail.com - 2013-04-27 20:42 -0700
Re: "python.exe has stopped working" when os.execl() runs on Windows 7 Terry Jan Reedy <tjreedy@udel.edu> - 2013-04-28 03:51 -0400
Re: "python.exe has stopped working" when os.execl() runs on Windows 7 cormogram@gmail.com - 2013-04-28 18:39 -0700
Re: "python.exe has stopped working" when os.execl() runs on Windows 7 Fábio Santos <fabiosantosart@gmail.com> - 2013-04-28 09:02 +0100
Re: "python.exe has stopped working" when os.execl() runs on Windows 7 cormogram@gmail.com - 2013-04-28 18:34 -0700
Re: "python.exe has stopped working" when os.execl() runs on Windows 7 Fábio Santos <fabiosantosart@gmail.com> - 2013-04-28 09:05 +0100
Re: "python.exe has stopped working" when os.execl() runs on Windows 7 cormogram@gmail.com - 2013-04-28 18:38 -0700
Re: "python.exe has stopped working" when os.execl() runs on Windows 7 Fábio Santos <fabiosantosart@gmail.com> - 2013-05-01 22:00 +0100
Re: "python.exe has stopped working" when os.execl() runs on Windows 7 Neil Cerutti <neilc@norwich.edu> - 2013-05-02 12:50 +0000
Re: "python.exe has stopped working" when os.execl() runs on Windows 7 Nobody <nobody@nowhere.com> - 2013-04-28 04:53 +0100
Re: "python.exe has stopped working" when os.execl() runs on Windows 7 cormogram@gmail.com - 2013-04-27 22:06 -0700
csiph-web