Can you point me at one such thing? It sounds like the answer is “yes” because I don’t really know that conforming to the dictates of whatever nonsense heuristics virus scanners use to detect “infections” is part of our remit, but I’m also not clear as to whether you’re saying that this is an issue with projects generated using
bdist_wininst or an issue with something about
bdist_wininst itself. I think we can wontfix any bug that is fixed by not using
In any case, to be clear, I am not saying we shouldn’t remove
bdist_wininst, I’m saying that we should remove it from
setuptools, and either not touch it in
distutils at all (or at least not until a decent interval of time after it’s been removed from
As it stands now, it was deprecated in 3.8 but not in
setuptools, which means the deprecation cycle for
setuptools hasn’t even started.
I suppose we could just import it wholesale into
setuptools and then go through the deprecation cycle there, but like I said, that creates extra needless work that could be solved by just having started this process in
setuptools and not
distutils in the first place (the project that the vast majority of people actually use for their builds).