Charles-François Natali added the comment: > Other parts of your reasoning are somewhat circular because most of the > problems on AIX are Linux-isms (or BSD-isms where BSD has not yielded to > Linux behavior). So you argue against adding lots of AIX-specific code, yet > fixing some of the tests more generally will require adding lots of > AIX-specific code.
It shouldn't require a lot of AIX-specific code, as long as AIX is POSIX-compliant. If some tests are failing because on Linux-isms assumptions - either in the stdlib, or in the tests - as I said, we'll be happy to fix them: just open relevant issues. Once again, this issue is not about whether or not we want to support AIX (I'm personally happy to have as many Unices supported as possible), but rather whether or not we want to add large chunks of OS-specific code, whereas the currently generic POSIX primitives - such as select() and poll() - work on all POSIX-compliant platforms. Adding platform-specific code has a cost, and IMO, the cost isn't worth it for AIX. I can understand that your point of view differs, either because of your job or personal interest, that's why I'd like to know if there's a consensus, or semi-official policy among the CPython project. Feel free to bring this up on the python-dev mailing list! ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue19302> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com