From c3de1766e7f1234b88db22103c534320c2a4d4db Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Martin=20v=2E=20L=C3=B6wis?= <martin@v.loewis.de>
Date: Sat, 27 Jun 2009 23:00:59 +0000
Subject: Bump Windows versions to 3.2.

---
 PCbuild/kill_python.c     | 2 +-
 PCbuild/pyproject.vsprops | 2 +-
 PCbuild/readme.txt        | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

(limited to 'PCbuild')

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.
diff --git a/PCbuild/pyproject.vsprops b/PCbuild/pyproject.vsprops
index 59163e6236..aa801a10d2 100644
--- a/PCbuild/pyproject.vsprops
+++ b/PCbuild/pyproject.vsprops
@@ -38,7 +38,7 @@
 	/>
 	<UserMacro
 		Name="PyDllName"
-		Value="python31"
+		Value="python32"
 	/>
 	<UserMacro
 		Name="PythonExe"
diff --git a/PCbuild/readme.txt b/PCbuild/readme.txt
index 918a1d3832..1a5f3012b3 100644
--- a/PCbuild/readme.txt
+++ b/PCbuild/readme.txt
@@ -37,7 +37,7 @@ NOTE:
    running a Python core buildbot test slave; see SUBPROJECTS below)
 
 When using the Debug setting, the output files have a _d added to
-their name:  python31_d.dll, python_d.exe, parser_d.pyd, and so on. Both
+their name:  python32_d.dll, python_d.exe, parser_d.pyd, and so on. Both
 the build and rt batch files accept a -d option for debug builds.
 
 The 32bit builds end up in the solution folder PCbuild while the x64 builds
-- 
cgit v1.2.1