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 ralf.gommers
Recipients BreamoreBoy, THRlWiTi, cgohlke, christian.heimes, dstufft, eric.araujo, loewis, max.naumov, paul.moore, ralf.gommers, silverbacknet, steve.dower, theller, tim.golden, trent
Date 2015-08-12.18:56:48
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I'll note that in Numpy we have now worked around the issue (with, basically by monkeypatching distutils and doing:

    if '/MANIFEST' not in ldflags:

The bug report is still valid though; it should not be specific to numpy. A more detailed report of what was broken before and fixed by this patch would have been helpful. I cannot be sure that this is 100% correct because I don't have Windows+MSVC available, but it should be this:

- Take Python 3.4 installed from the .exe installer
- Create a new virtualenv and activate it
- pip install numpy==1.8.0   # this will fail
- apply the patch
- pip install numpy==1.8.0   # this will work

Furthermore I think that this is a duplicate of, which is also a valid bug report confirmed by multiple people (but closed as "not a bug"). 

Given that applying the patch is harmless and not applying it clearly does create problems for users, it would make sense to apply it. But honestly, given for how long the bug reports on 4431 were ignored, I'm not willing to spend much effort on this. So if no one else does either, this issue may indeed just as well be closed as outdated like Marc Lawrence suggests.
Date User Action Args
2015-08-12 18:56:48ralf.gommerssetrecipients: + ralf.gommers, loewis, theller, paul.moore, christian.heimes, tim.golden, trent, eric.araujo, cgohlke, THRlWiTi, silverbacknet, BreamoreBoy, steve.dower, dstufft, max.naumov
2015-08-12 18:56:48ralf.gommerssetmessageid: <>
2015-08-12 18:56:48ralf.gommerslinkissue16296 messages
2015-08-12 18:56:48ralf.gommerscreate