On Tue, Mar 5, 2013 at 2:35 AM, Tomas Kotal wrote:
> Seems like I found the problem: os._exit probably takes as parametr unsigned
> char, so it uses as error code whatever value it gets modulo 256:
>
> os._exit(1) # process.exitcode == 1
> os._exit(255) # process.exitcode == 255
> os._exit(256)
Dne pondělí, 4. března 2013 15:31:41 UTC+1 Tomas Kotal napsal(a):
> Hi all.
>
>
>
> Recently I discovered a strange behavior with multiprocessing library and
> call to function os.system (a different behavior under Linux and Windows to
> be more specific). I have this simple testing script:
>
> Under Unix, the return value from os.system() encodes more than one
>
> piece of information:
>
>
>
> http://docs.python.org/2/library/os.html#os.system
>
> http://docs.python.org/2/library/os.html#os.wait
>
>
>
> 32512 is 127*256, meaning that the shell exited with return code 127
>
> w
On Tue, Mar 5, 2013 at 1:31 AM, Tomas Kotal wrote:
> But when I run same script on Linux, what I get is this:
>
> 0
> 32512
Under Unix, the return value from os.system() encodes more than one
piece of information:
http://docs.python.org/2/library/os.html#os.system
http://docs.python.org/2/librar
Hi all.
Recently I discovered a strange behavior with multiprocessing library and call
to function os.system (a different behavior under Linux and Windows to be more
specific). I have this simple testing script:
import sys
import os
from multiprocess
