Steve Dower added the comment: I suspect that should be filed as a bug against VS 2017 - I'll do that when I get to work on Monday.
Our workaround should be to check for that targets file and keep searching if it's not found. Your best workaround is to start the build from the VS 2015 developer command prompt, which will have the right MSBuild on PATH and will bypass the search. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue30687> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
