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 | mishok13 |
|---|---|
| Recipients | donmez, mishok13 |
| Date | 2008年05月16日.08:55:26 |
| SpamBayes Score | 0.03604214 |
| Marked as misclassified | No |
| Message-id | <1210928131.33.0.740217939164.issue2890@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
>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 |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年05月16日 08:55:31 | mishok13 | set | spambayes_score: 0.0360421 -> 0.03604214 recipients: + mishok13, donmez |
| 2008年05月16日 08:55:31 | mishok13 | set | spambayes_score: 0.0360421 -> 0.0360421 messageid: <1210928131.33.0.740217939164.issue2890@psf.upfronthosting.co.za> |
| 2008年05月16日 08:55:28 | mishok13 | link | issue2890 messages |
| 2008年05月16日 08:55:27 | mishok13 | create | |