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 ncoghlan
Recipients docs@python, matham, ncoghlan, r.david.murray, steve.dower, tim.golden, zach.ware
Date 2015-03-26.02:19:17
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1427336358.47.0.890858742797.issue23743@psf.upfronthosting.co.za>
In-reply-to
Content
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 :)
History
Date User Action Args
2015-03-26 02:19:18ncoghlansetrecipients: + ncoghlan, tim.golden, r.david.murray, docs@python, zach.ware, steve.dower, matham
2015-03-26 02:19:18ncoghlansetmessageid: <1427336358.47.0.890858742797.issue23743@psf.upfronthosting.co.za>
2015-03-26 02:19:18ncoghlanlinkissue23743 messages
2015-03-26 02:19:17ncoghlancreate