Éric Araujo added the comment: > both wheel/pip makes calls to distutils.util.get_platform(). Fixing it in one > location > would fix it across the board.
True, but it may have unintended effects in other places that disrupt or break parts of the CPython build process, or downstream packaging toolchains. > using just distutils.core.setup() and doing a bdist (built-in command > available in > distutils) is still generating a wrong tag in linux 32-bit arch. I would say that this is irrelevant, since these kinds of bdist are not well defined and not really used. > within distutils.util.get_platform() the code under sunos makes attempts to > identify the > correct bitness: [...] > why would the linux logic not handle the same problem? That’s always the question with distutils, and the reason for us being over-cautious with these requests for changes. One needs to do VCS archaeology to understand if a specific line was a conscious decision, an assumption, an oversight or a mistake. My suggestion of bringing this to setuptools is because they have a much faster release cycle, and broad testing. They can change only the wheel compatibility tags and get feedback immediately, whereas changing distutils.util.get_plaform may break many things and we’ll only know in a couple years when the next release is packaged by distributions and third-party vendors. [removing Raymond from nosy and adding Jason the setuptools maintainer] ---------- nosy: +jason.coombs -rhettinger _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue31211> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
