➜

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 vstinner
Recipients Arfrever, Jelmer Vernooij, amaury.forgeotdarc, eric.araujo, hroncok, jelmer, loewis, runtux, tarek, techtonik, vstinner
Date 2019-07-01.11:03:29
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1561979009.33.0.943685145084.issue10945@roundup.psfhosted.org>
In-reply-to
Content 
> I've opened a PR thet removes the support for bdist_wininst on non-Windows. Apparently, it was broken since the beginning of Py3k anyway. The support can be reintroduced once it is actually fixed (or never).

It would be better to use the Unicode (wide character) flavor of the Windows API to avoid completely any explicitly encoding, and only pass Unicode strings. But This issue is open for 8 years and it seems like nobody cares enough to invest time to implement such change.

So I'm fine with trivial PR 14506. It doesn't change the status quo: bdist_win was always broken on non-Windows platforms since Python 3.0, but the PR makes the status quo more obvious which is a good thing.
History
Date User Action Args
2019-07-01 11:03:29vstinnersetrecipients: + vstinner, loewis, amaury.forgeotdarc, techtonik, tarek, eric.araujo, Arfrever, jelmer, runtux, hroncok, Jelmer Vernooij
2019-07-01 11:03:29vstinnersetmessageid: <1561979009.33.0.943685145084.issue10945@roundup.psfhosted.org>
2019-07-01 11:03:29vstinnerlinkissue10945 messages
2019-07-01 11:03:29vstinnercreate