Nick Coghlan added the comment:

pypa.io hosts the internal dev docs for PyPA, I believe you meant 
packaging.python.org, and that would indeed be the right home.

However, this kind of C/C++ linker related problem is way too advanced for the 
current state of the binary extension docs which basically say "C/C++ is hard 
relative to Python, let someone else deal with creating your extension modules 
for you": https://packaging.python.org/en/latest/extensions.html

For the scientific stack in particular we go even further and say to get 
someone else to build and link the extension modules for you: 
https://packaging.python.org/en/latest/science.html

Folks encountering the kind of problem described in this issue is thus mostly 
useful as a data point in *why* we give those instructions: because DIY 
cross-platform C/C++ development is a teeming morass of "fun" interoperability 
bugs like this one just waiting to be discovered :)

----------

_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue23743>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Reply via email to