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 njs
Recipients Ray Donnelly, barry, brett.cannon, eryksun, lemburg, njs, paul.moore, steve.dower, tim.golden, xoviat, zach.ware
Date 2018-01-17.03:53:54
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1516161234.52.0.467229070634.issue32516@psf.upfronthosting.co.za>
In-reply-to
Content
> That looks like recompilation (or at least how recompilation would look if you'd been granted permission). Assuming you can recompile the binary, you could rename the dependency and regenerate the import library so that you can link directly against the new name.

Perhaps *you* can do that, but I don't think you want to volunteer to maintain Windows wheels for every package on PyPI :-). Regenerating import libraries and tweaking build systems and all that works fine if you're a Windows specialist distributing artisinal hand-crafted builds, but you can't automate that knowledge and use it at scale. You *can* write an automatic tool that slurps in a bunch of PE files and rewrites them to create a self-contained DLL-hell-free redistributable. This is the core strategy that osx and manylinux wheels have been using for years now, and why it's possible for random devs to make wheels that work, even on platforms they don't use.
History
Date User Action Args
2018-01-17 03:53:54njssetrecipients: + njs, lemburg, barry, brett.cannon, paul.moore, tim.golden, zach.ware, eryksun, steve.dower, xoviat, Ray Donnelly
2018-01-17 03:53:54njssetmessageid: <1516161234.52.0.467229070634.issue32516@psf.upfronthosting.co.za>
2018-01-17 03:53:54njslinkissue32516 messages
2018-01-17 03:53:54njscreate