[issue2890] O_ASYNC and FASYNC should be defined for *nix systems
Andrii V. Mishkovskyi
report at bugs.python.org
Fri May 16 10:55:31 CEST 2008
Andrii V. Mishkovskyi <mishok13 at gmail.com> added the comment:
>I think they at least should be supported on Linux then.
And what happens if some Unix flavor (i.e. Solaris) adds new flag, say
O_NONLINUXSYNC and it has the same value as linux's O_ASYNC? And then
FreeBSD adds O_BSDSYNC flag with the same number and so on. Then Python
will have to have separate system-specific module for each *nix system
that uses Python. Why do you think Python maintainers would want that?
>It does work if you use the value itself anyway.
It's the way fcntl works -- it's just a thin layer on top of fcntl() and
ioctl() calls. But that's not a good reason for including non-posix
flags to 'posix' module
__________________________________
Tracker <report at bugs.python.org>
<http://bugs.python.org/issue2890>
__________________________________
More information about the Python-bugs-list
mailing list