[issue28680] bdist_wininst generated 64-bit executable looks for 3.5-32

Steve Dower added the comment: Fixed for 3.5.3, 3.6.1 and default against the original issue26071 -- resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> bdist_wininst created binaries fail to start and find 32bit Pythons

[issue28680] bdist_wininst generated 64-bit executable looks for 3.5-32

Changes by Steve Dower : -- assignee: -> steve.dower keywords: +3.4regression versions: +Python 3.7 ___ Python tracker ___ ___ Python

[issue28680] bdist_wininst generated 64-bit executable looks for 3.5-32

Steve Dower added the comment: Thanks. 3.5.3 is definite, I've pinged the release manage on the original bug to see about 3.6.0, but definitely 3.6.1. Considering we've gone through all of 3.5 and 3.6 with very few people noticing (and as far as I'm aware, completely able to fix it themselves)

[issue28680] bdist_wininst generated 64-bit executable looks for 3.5-32

Christoph Gohlke added the comment: The attached patch was tested with Pillow-3.4.2 on Python 3.6.0rc1, 32-bit and 64-bit. It would be nice to get this fixed in Python 3.5.3 and 3.6.0. -- components: +Windows keywords: +patch nosy: +paul.moore, steve.dower, tim.golden, zach.ware Added

[issue28680] bdist_wininst generated 64-bit executable looks for 3.5-32

Christoph Gohlke added the comment: Pillow-3.4.2.win-amd64-py3.5.exe fails to install due to this. See . `MS_WIN64` is never defined at because bdist_wininst does n

[issue28680] bdist_wininst generated 64-bit executable looks for 3.5-32

New submission from Timothy Widrick: Short version: wininst-14.0-amd64.exe has "-32" in it. It shouldn't, should it? Longer version: Running "python setup.py bdist_wininst" gives me a file named like: project-version.win-amd64-py3.5.exe When I run that, I get: Python version 3.5-32 r