More 3.0 -> 3.1 transistion in the Windows and OS/2 build files

2 files changed, 3 insertions, 3 deletions

diff --git a/PC/VS8.0/build_ssl.bat b/PC/VS8.0/build_ssl.bat
index 04eab5b..4effc6f 100644
--- a/PC/VS8.0/build_ssl.bat
+++ b/PC/VS8.0/build_ssl.bat
@@ -2,10 +2,10 @@
 if not defined HOST_PYTHON (

   if %1 EQU Debug (

     set HOST_PYTHON=python_d.exe

-    if not exist python30_d.dll exit 1

+    if not exist python31_d.dll exit 1

   ) ELSE (

     set HOST_PYTHON=python.exe

-    if not exist python30.dll exit 1

+    if not exist python31.dll exit 1

   )

 )

 %HOST_PYTHON% build_ssl.py %1 %2 %3

diff --git a/PC/VS8.0/kill_python.c b/PC/VS8.0/kill_python.c
index f3880fc..17a5f32 100644
--- a/PC/VS8.0/kill_python.c
+++ b/PC/VS8.0/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. python30[_d].dll),
+         * and see if any of our DLLs are loaded (i.e. python31[_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.