[issue14877] No option to run bdist_wininst against newer msvc versions on non-windows systems

STINNER Victor added the comment: The distutils bdist_wininst command has been removed in Python 3.10: see bpo-42802. -- nosy: +vstinner resolution: -> wont fix stage: -> resolved status: open -> closed ___ Python tracker

[issue14877] No option to run bdist_wininst against newer msvc versions on non-windows systems

Aaron Staley added the comment: Hi Eric, Quick rundown: There are template 'exe' inside distutils/command. bdist_wininst appends to the template to build a customized installer. First the 64 bit bug: http://bugs.python.org/issue6792 With that bug active, I must be able to make 64 bit window

[issue14877] No option to run bdist_wininst against newer msvc versions on non-windows systems

Éric Araujo added the comment: Thanks for the report. I know little about the wininst code in distutils; can you explain if this is a bug (i.e. bdist_wininst in 2.7 must use wininst-9.0-etc.exe or the installers won’t work) or a feature request (i.e. a new option to allow using newer exe fil

[issue14877] No option to run bdist_wininst against newer msvc versions on non-windows systems

Aaron Staley added the comment: Sorry, minor correction: We could just rely on plat_name for 64bit. All that is needed is for this table: if self.target_version < "2.4": bv = 6.0 else: bv = 7.1 to be updated to python2.

[issue14877] No option to run bdist_wininst against newer msvc versions on non-windows systems

New submission from Aaron Staley : On a *nix system, bdist_wininst.get_exe_bytes will always return an open wininst-6.0.exe. However, Windows python2.7 is compiled against msvc 9.0 and ideally would take an installer based on wininst-9.0.exe. Windows-64bit needs an installer based on winins