➜

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 serhiy.storchaka
Recipients gregory.p.smith, pablogsal, ronaldoussoren, serhiy.storchaka, vstinner
Date 2018-09-18.14:18:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1537280282.17.0.956365154283.issue34663@psf.upfronthosting.co.za>
In-reply-to
Content 
If glibc already uses vfork() if it is safe, I suppose that using vfork() in other cases is unsafe, and we shouldn't support this nonstandard option.
History
Date User Action Args
2018-09-18 14:18:02serhiy.storchakasetrecipients: + serhiy.storchaka, gregory.p.smith, ronaldoussoren, vstinner, pablogsal
2018-09-18 14:18:02serhiy.storchakasetmessageid: <1537280282.17.0.956365154283.issue34663@psf.upfronthosting.co.za>
2018-09-18 14:18:02serhiy.storchakalinkissue34663 messages
2018-09-18 14:18:02serhiy.storchakacreate