Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #40449

Re: Different behavior with multiprocessing

References <c25680d3-6814-4d5f-a5a2-aa4b9bb0c3a0@googlegroups.com>
Date 2013-03-05 01:58 +1100
Subject Re: Different behavior with multiprocessing
From Chris Angelico <rosuav@gmail.com>
Newsgroups comp.lang.python
Message-ID <mailman.2840.1362409142.2939.python-list@python.org> (permalink)

Show all headers | View raw


On Tue, Mar 5, 2013 at 1:31 AM, Tomas Kotal <tomas.kotal@gmail.com> 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/library/os.html#os.wait

32512 is 127*256, meaning that the shell exited with return code 127
when given an unrecognized command.

ChrisA

Back to comp.lang.python | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Different behavior with multiprocessing Tomas Kotal <tomas.kotal@gmail.com> - 2013-03-04 06:31 -0800
  Re: Different behavior with multiprocessing Chris Angelico <rosuav@gmail.com> - 2013-03-05 01:58 +1100
    Re: Different behavior with multiprocessing Tomas Kotal <tomas.kotal@gmail.com> - 2013-03-04 07:12 -0800
    Re: Different behavior with multiprocessing Tomas Kotal <tomas.kotal@gmail.com> - 2013-03-04 07:12 -0800
  Re: Different behavior with multiprocessing Tomas Kotal <tomas.kotal@gmail.com> - 2013-03-04 07:35 -0800
    Re: Different behavior with multiprocessing Chris Angelico <rosuav@gmail.com> - 2013-03-05 02:44 +1100

csiph-web