[issue10136] kill_python doesn't work with short path

Zachary Ware added the comment: If anybody actually has a problem with this in future, they can reopen the issue and try using GetFullPathName as Steve suggested. -- resolution: -> wont fix stage: -> resolved status: open -> closed ___ Python track

[issue10136] kill_python doesn't work with short path

Steve Dower added the comment: My usual way of doing this is to use taskkill.exe, but that only uses process name and not the full path, which may hurt people who are building with other versions of Python open. I'd rather use GetFullPathName than the current patch, but if wontfix is the pref

[issue10136] kill_python doesn't work with short path

Tim Golden added the comment: +1 -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mai

[issue10136] kill_python doesn't work with short path

Zachary Ware added the comment: I'm inclined to close as 'won't fix'; kill_python.exe is an "eh, good enough" hack meant mostly for the buildbots anyway, and short paths are exceptionally rare these days. If anything, I'd just add a warning that if "~" is in the path, all bets are off. -

[issue10136] kill_python doesn't work with short path

Changes by Ned Deily : -- components: +Windows -Build nosy: +steve.dower, tim.golden, zach.ware ___ Python tracker ___ ___ Python-bugs

[issue10136] kill_python doesn't work with short path

Mark Lawrence added the comment: Can somebody review the attached patch please. -- nosy: +BreamoreBoy versions: +Python 3.4, Python 3.5 -Python 3.1, Python 3.2 ___ Python tracker ___

[issue10136] kill_python doesn't work with short path

New submission from Hirokazu Yamamoto : When kill_python[,d].exe was called via short path, no python processes won't be killed. This happens because, directory path is compared via simple wcsnicmp. If one is short path and another is long path, wcsnicmp determines they are not same path. This pa