Message142321
| Author |
pitrou |
| Recipients |
David.Townshend, Julian, benjamin.peterson, docs@python, neologix, pitrou, vstinner |
| Date |
2011年08月18日.14:19:16 |
| SpamBayes Score |
1.2928052e-06 |
| Marked as misclassified |
No |
| Message-id |
<1313677026.3602.2.camel@localhost.localdomain> |
| In-reply-to |
<CAH_1eM3tWTZeWEMPQQqh8X7ykezhjOw-_dU5UgPgdtVMwX3ZKg@mail.gmail.com> |
| Content |
> Well, I'd rather have this flag called 'x', to be consistent with
> glibc's fopen():
>
> """
> c (since glibc 2.3.3)
> Do not make the open operation, or subsequent read and write
> operations, thread cancellation points.
>
> x Open the file exclusively (like the O_EXCL flag of
> open(2)). If the
> file already exists, fopen() fails, and sets errno to
> EEXIST. This
> flag is ignored for fdopen().
Yeah, but I think "exclusively" is quite misleading since it does not
perform any locking of any kind. Also, I don't think we'll ever
integrate the glibc's "c" option in io.open(). |
|