Message 136353 - Python tracker

➜

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	socketpair
Recipients	alexey-smirnov, amaury.forgeotdarc, neologix, socketpair, vstinner
Date	2011-05-20.04:55:46
SpamBayes Score	5.636516e-07
Marked as misclassified	No
Message-id	<[email protected]>
In-reply-to

Content
Why not to implement 'e' letter in py3k ? In systems where O_CLOEXEC is not supported in open(), flag should be set non-atomically using fcntl. To exclude races (in concurrent threads), this two ops should be done under lock (GIL?)

Why not to implement 'e' letter in py3k ?

In systems where O_CLOEXEC is not supported in open(), flag should be set non-atomically using fcntl.

To exclude races (in concurrent threads), this two ops should be done under lock (GIL?)

History
Date	User	Action	Args
2011-05-20 04:55:48	socketpair	set	recipients: + socketpair, amaury.forgeotdarc, vstinner, neologix, alexey-smirnov
2011-05-20 04:55:48	socketpair	set	messageid: <[email protected]>
2011-05-20 04:55:46	socketpair	link	issue12105 messages
2011-05-20 04:55:46	socketpair	create