This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author jort.bloem
Recipients jort.bloem, r.david.murray, vstinner
Date 2013-02-19.00:30:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1361233822.0.0.323452330914.issue17230@psf.upfronthosting.co.za>
In-reply-to
Content
haypo: I understand that, after a fork, parent and child instructions are run in parallel; which one prints first is a matter of chance.

However, commands BEFORE THE FORK should not be re-run.

See test script. I would expect one "Start <pid>", followed by a "parent <pid>" and a "child <pid>". I would not expect to see (as I do) a second "Start <pid>".

(The original program was long and complex, with numerous forks; this is the smallest program I could write to show the problem).
History
Date User Action Args
2013-02-19 00:30:22jort.bloemsetrecipients: + jort.bloem, vstinner, r.david.murray
2013-02-19 00:30:22jort.bloemsetmessageid: <1361233822.0.0.323452330914.issue17230@psf.upfronthosting.co.za>
2013-02-19 00:30:21jort.bloemlinkissue17230 messages
2013-02-19 00:30:21jort.bloemcreate