[pywin32-checkins] pywin32 setup_win32all.py,1.5,1.6

[<mha...@us...>]

Update of /cvsroot/pywin32/pywin32
In directory sc8-pr-cvs1:/tmp/cvs-serv17422

Modified Files:
	setup_win32all.py 
Log Message:
Update comments and docstrings.


Index: setup_win32all.py
===================================================================
RCS file: /cvsroot/pywin32/pywin32/setup_win32all.py,v
retrieving revision 1.5
retrieving revision 1.6
diff -C2 -d -r1.5 -r1.6
*** setup_win32all.py	3 Dec 2003 08:11:27 -0000	1.5
--- setup_win32all.py	3 Dec 2003 09:04:07 -0000	1.6
***************
*** 5,14 ****
  
  These extensions require a number of libraries to build, some of which may
! require your to install special SDKs or toolkits.  This script will attempt
! to build as many as it can, and at the end of the build, will report any 
! extension modules that could not be built and why.  Not being able to build
! the MAPI or ActiveScripting related projects is common.
! If you don't use these extensions, you can ignore these warnings; if you do
! use them, you must install the correct libraries.
  
  To install the win32all extensions, execute:
--- 5,18 ----
  
  These extensions require a number of libraries to build, some of which may
! require you to install special SDKs or toolkits.  This script will attempt
! to build as many as it can, and at the end of the build will report any 
! extension modules that could not be built and why.  Early versions of
! certain Windows headers will also cause certain modules to be skipped (in
! general, the latest "Platform SDK" from:
!   http://www.microsoft.com/msdownload/platformsdk/sdkupdate
! should be used.
! 
! If you don't use the extensions that fail to build, you can ignore these
! warnings; if you do use them, you must install the correct libraries.
  
  To install the win32all extensions, execute:
***************
*** 19,28 ****
  There should be no need to modify the registry.
  
! To build or install debug (_d) versions of these extensions, pass the "--debug"
  flag to the build command - eg:
    python setup_win32all.py -q build --debug
  or to build and install a debug version:
    python setup_win32all.py -q build --debug install
- you must have built (or installed) a debug version of Python for this to work.
  """
  # Thomas Heller, started in 2000 or so.
--- 23,32 ----
  There should be no need to modify the registry.
  
! To build or install debug (_d) versions of these extensions, ensure you have
! built or installed a debug version of Python itself, then pass the "--debug"
  flag to the build command - eg:
    python setup_win32all.py -q build --debug
  or to build and install a debug version:
    python setup_win32all.py -q build --debug install
  """
  # Thomas Heller, started in 2000 or so.
***************
*** 889,896 ****
  # some 'no wait' executor - spawn seems fine!  We pass the PID of this
  # process so the child will wait for us.
  if not dist.dry_run and dist.command_obj.has_key('install') \
         and not dist.command_obj.has_key('bdist_wininst'):
!     # What executable to use?  This one I guess.  Maybe I could just import
!     # as a module and execute?
      filename = os.path.join(
                    os.path.dirname(sys.argv[0]), "pywin32_postinstall.py")
--- 893,901 ----
  # some 'no wait' executor - spawn seems fine!  We pass the PID of this
  # process so the child will wait for us.
+ # XXX - hmm - a closer look at distutils shows it only uses win32api
+ # if _winreg fails - and this never should.  Need to revisit this!
  if not dist.dry_run and dist.command_obj.has_key('install') \
         and not dist.command_obj.has_key('bdist_wininst'):
!     # What executable to use?  This one I guess.
      filename = os.path.join(
                    os.path.dirname(sys.argv[0]), "pywin32_postinstall.py")