➜

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.15:57:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1537286222.24.0.956365154283.issue34663@psf.upfronthosting.co.za>
In-reply-to
Content 
You still need to allow the flag as being safe or unsafe depends on the user code as glibc cannot know about the details of what is going to be executed. That is the reason they have the flag, so the user can disambiguate if is safe or not. If we don't expose the flag, the user may know that what is going to do is safe or acceptable but then they cannot activate the use of vfork.
History
Date User Action Args
2018-09-18 15:57:02pablogsalsetrecipients: + pablogsal, gregory.p.smith, ronaldoussoren, vstinner, serhiy.storchaka
2018-09-18 15:57:02pablogsalsetmessageid: <1537286222.24.0.956365154283.issue34663@psf.upfronthosting.co.za>
2018-09-18 15:57:02pablogsallinkissue34663 messages
2018-09-18 15:57:02pablogsalcreate