➜

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 pablogsal
Recipients gregory.p.smith, pablogsal, ronaldoussoren, serhiy.storchaka, vstinner
Date 2018-09-18.11:27:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1537270020.68.0.956365154283.issue34663@psf.upfronthosting.co.za>
In-reply-to
Content 
The documentation says:

 The child process is created using vfork(2) instead of fork(2) when
       either of the following is true:

       *  the spawn-flags element of the attributes object pointed to by
          attrp contains the GNU-specific flag POSIX_SPAWN_USEVFORK; or

       *  file_actions is NULL and the spawn-flags element of the attributes
          object pointed to by attrp does not contain
          POSIX_SPAWN_SETSIGMASK, POSIX_SPAWN_SETSIGDEF,
          POSIX_SPAWN_SETSCHEDPARAM, POSIX_SPAWN_SETSCHEDULER,
          POSIX_SPAWN_SETPGROUP, or POSIX_SPAWN_RESETIDS.

So using the flag is necessary if you want to force the use of vfork when passing any of the flags specified in the second point.
History
Date User Action Args
2018-09-18 11:27:00pablogsalsetrecipients: + pablogsal, gregory.p.smith, ronaldoussoren, vstinner, serhiy.storchaka
2018-09-18 11:27:00pablogsalsetmessageid: <1537270020.68.0.956365154283.issue34663@psf.upfronthosting.co.za>
2018-09-18 11:27:00pablogsallinkissue34663 messages
2018-09-18 11:27:00pablogsalcreate