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 paul.moore
Recipients bgilbert, jaharkes, mrabarnett, paul.moore, python-dev, steve.dower, tim.golden, zach.ware
Date 2015-06-08.17:29:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1433784597.68.0.44841113854.issue24385@psf.upfronthosting.co.za>
In-reply-to
Content
I'm still somewhat confused as to why we're looking at this in the context of manually building an extension. It's *certainly* true that anyone attempting to build a Python extension by hand (as per Matthew Barnett's instructions) should be able and willing to build the import libraries by hand.

On the other hand, I've no *objection* to shipping the .a files (and I agree 100% that shipping a 64-bit library in a 32-bit installer is a bug). But if we do so, then we should be shipping whatever makes setup.py build_ext --compiler=mingw (i.e. distutils) happy. Distutils is the only way of building extensions that I think we should support (whether via shipping .a files, or in terms of how we handle any other bug reports).
History
Date User Action Args
2015-06-08 17:29:57paul.mooresetrecipients: + paul.moore, tim.golden, mrabarnett, python-dev, bgilbert, zach.ware, steve.dower, jaharkes
2015-06-08 17:29:57paul.mooresetmessageid: <1433784597.68.0.44841113854.issue24385@psf.upfronthosting.co.za>
2015-06-08 17:29:57paul.moorelinkissue24385 messages
2015-06-08 17:29:57paul.moorecreate