➜

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 steve.dower, vstinner, zach.ware
Date 2019-06-25.10:38:36
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1561459116.66.0.739442467259.issue37396@roundup.psfhosted.org>
In-reply-to
Content 
> How can you tell that $(PyDebugExt) is not set?  Note that the "Killing any running python.exe instances..." line is hard-coded, it does not currently include $(PyDebugExt) (though it probably should).  Adding that to the message would be a good first step; ...

Oh... I didn't notice :-) I wrote PR 14370 to fix that.


> ...; backporting GH-9901 to 2.7 would probably also be good even though it was solving a different issue.

I'm not brave enough yet to make such large changes into Python 2.7 build system on Windows. I'm unable to build Python 2.7 for Windows for at least one year...
History
Date User Action Args
2019-06-25 10:38:36vstinnersetrecipients: + vstinner, zach.ware, steve.dower
2019-06-25 10:38:36vstinnersetmessageid: <1561459116.66.0.739442467259.issue37396@roundup.psfhosted.org>
2019-06-25 10:38:36vstinnerlinkissue37396 messages
2019-06-25 10:38:36vstinnercreate