[issue12105] open() does not able to set flags, such as O_CLOEXEC

[STINNER Victor]

STINNER Victor <victor.stinner at haypocalc.com> added the comment:

> One moment -- adding a new value to the os module looks like a new
> feature to me.  Is there any convincing reason why this needs to go to
> 3.2?  (And it most definitely shouldn't go to 3.1.)

Python doesn't suppose atomic open+CLOEXEC anymore, I consider this as a
regression from Python 2 (which support open("re") with the GNU libc).
Because the patch is simple, I think that it can go in 3.1 and 3.2. Am I
wrong? But... it tooks some years until someone noticed this regression.

Can we add new features to old releases?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue12105>
_______________________________________