Marc-Andre Lemburg added the comment: On 16.04.2015 18:12, Nick Coghlan wrote: > > I can tell you exactly where these files need to live side by side: index > servers. We currently paper over it on PyPI for Windows and Mac OS X by > leveraging the implicitly defined ABI compatibility of the CPython binary > releases published on python.org, but that starts to break down as soon as > people are using interpreter binaries built locally or by redistributors > rather than by the CPython core development team. There's more to the > computing world than Intel CPU architectures, and more kernel APIs than > Linux, Darwin and Windows.
But that's a completely different use case than what's being addressed in this ticket: This ticket is about C extension files, not packages or custom Python interpreter binary names. For packages, I agree, we would benefit from a more standardized ABI naming scheme that what setuptools or distutils currently have to offer. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue22980> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
