Message136445
| Author |
Christophe.Devriese |
| Recipients |
Christophe.Devriese, gregory.p.smith, nadeem.vawda, neologix |
| Date |
2011年05月21日.14:35:32 |
| SpamBayes Score |
6.99236e-05 |
| Marked as misclassified |
No |
| Message-id |
<BANLkTi=-A5JcEoRXsyEAi1fUo9tmm--_kA@mail.gmail.com> |
| In-reply-to |
<1305933892.11.0.730865118331.issue12107@psf.upfronthosting.co.za> |
| Content |
It would already be a nice piece of progress if you could request the
SO_CLOEXEC (with fallback to FD_CLOEXEC), say, in the constructor, or even
with a module variable. I hope at least this change can make it in, so that
we have a decent in-python solution that can be used from within, say,
django.
Christophe
On Sat, May 21, 2011 at 1:24 AM, Antoine Pitrou <report@bugs.python.org>wrote:
>
> Changes by Antoine Pitrou <pitrou@free.fr>:
>
>
> Removed file: http://bugs.python.org/file22038/unnamed
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue12107>
> _______________________________________
> |
| Files |
|---|
| File name |
Uploaded |
|
unnamed
|
Christophe.Devriese,
2011年05月21日.14:35:32
|
|