summaryrefslogtreecommitdiff
path: root/PCbuild/kill_python.c
diff options
context:
space:
mode:
authorAndrew Svetlov <andrew.svetlov@gmail.com>2012-10-17 17:33:26 +0300
committerAndrew Svetlov <andrew.svetlov@gmail.com>2012-10-17 17:33:26 +0300
commit79ca8edc5b262cea550f10b231ab8eba90b267f3 (patch)
treeceff0896bcc2a98beb282e57524cb6829789ca3b /PCbuild/kill_python.c
parent69967aa2b5fe2461086c2d9b8942e2b24067ee75 (diff)
parent9f5126df5d121d4a03a3c91d29bb6e24f48ce7f7 (diff)
downloadcpython-79ca8edc5b262cea550f10b231ab8eba90b267f3.tar.gz
merge heads
Diffstat (limited to 'PCbuild/kill_python.c')
-rw-r--r--PCbuild/kill_python.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/PCbuild/kill_python.c b/PCbuild/kill_python.c
index bb323d31d0..604731f3f8 100644
--- a/PCbuild/kill_python.c
+++ b/PCbuild/kill_python.c
@@ -106,7 +106,7 @@ main(int argc, char **argv)
/*
* XXX TODO: if we really wanted to be fancy, we could check the
* modules for all processes (not just the python[_d].exe ones)
- * and see if any of our DLLs are loaded (i.e. python33[_d].dll),
+ * and see if any of our DLLs are loaded (i.e. python34[_d].dll),
* as that would also inhibit our ability to rebuild the solution.
* Not worth loosing sleep over though; for now, a simple check
* for just the python executable should be sufficient.