summaryrefslogtreecommitdiff
path: root/PCbuild/kill_python.c
diff options
context:
space:
mode:
authorMartin v. Löwis <martin@v.loewis.de>2009-06-27 23:00:59 +0000
committerMartin v. Löwis <martin@v.loewis.de>2009-06-27 23:00:59 +0000
commitc3de1766e7f1234b88db22103c534320c2a4d4db (patch)
treedafe2e1d3bd22832ffda43afd9656d1ba3782f70 /PCbuild/kill_python.c
parent4cf35c1969129f85bba438fb2ef66589a185bd24 (diff)
downloadcpython-c3de1766e7f1234b88db22103c534320c2a4d4db.tar.gz
Bump Windows versions to 3.2.
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 17a5f32ab2..6b916781cc 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. python31[_d].dll),
+ * and see if any of our DLLs are loaded (i.e. python32[_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.