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 | pitrou |
|---|---|
| Recipients | alexey-smirnov, amaury.forgeotdarc, christian.heimes, neologix, pitrou, rosslagerwall, sbt, vstinner |
| Date | 2013年01月03日.20:02:08 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1357243328.2.0.471447011384.issue16850@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
> How about two options, like 'e' for guaranteed atomic CLOEXEC and 'E' > for CLOEXEC with or without atomic ops? Why would you want that? Best effort is sufficient. Also, I'm not sure why "e". |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2013年01月03日 20:02:08 | pitrou | set | recipients: + pitrou, amaury.forgeotdarc, vstinner, christian.heimes, neologix, rosslagerwall, sbt, alexey-smirnov |
| 2013年01月03日 20:02:08 | pitrou | set | messageid: <1357243328.2.0.471447011384.issue16850@psf.upfronthosting.co.za> |
| 2013年01月03日 20:02:08 | pitrou | link | issue16850 messages |
| 2013年01月03日 20:02:08 | pitrou | create | |