[Python-checkins] CVS: python/nondist/peps pep-0101.txt,1.10,1.11

[Barry Warsaw]

Update of /cvsroot/python/python/nondist/peps
In directory usw-pr-cvs1:/tmp/cvs-serv25249

Modified Files:
	pep-0101.txt 
Log Message:
Integrated some of Guido's comments.


Index: pep-0101.txt
===================================================================
RCS file: /cvsroot/python/python/nondist/peps/pep-0101.txt,v
retrieving revision 1.10
retrieving revision 1.11
diff -C2 -d -r1.10 -r1.11
*** pep-0101.txt	2001/10/24 23:18:46	1.10
--- pep-0101.txt	2001/10/25 05:19:19	1.11
***************
*** 109,115 ****
        decide whether the change should also be applied to the branch.
  
!       Note that committers of changes to the trunk SHOULD include a
!       in the checkin message, a note indicating the suitability of
!       their patch for the branch.
  
        If so, it's fairly easy to apply the change by diff'ing the file
--- 109,115 ----
        decide whether the change should also be applied to the branch.
  
!       Note that committers of changes to the trunk SHOULD include in
!       the checkin message, a note indicating the suitability of their
!       patch for the branch.
  
        If so, it's fairly easy to apply the change by diff'ing the file
***************
*** 523,555 ****
  Windows Notes
  
!     Windows has a GUI installer, various flavors of Windows have "special
!     limitations", and the Windows installer also packs precompiled
!     "foreign" binaries (Tcl/Tk, expat, etc).  So Windows testing is
!     tiresome but very necessary.
  
!     Concurrent with uploading the installer, I install Python from it
!     twice:  once into the default directory suggested by the installer,
!     and later into a directory with embedded spaces in its name.  For
!     each installation, run the full regression suite from a DOS box, and
!     both with and without -0.  Also try *every* shortcut created under
!     Start -> Menu -> the Python group.  When trying IDLE this way, verify
!     that Help -> Python Documentation works.  When trying pydoc this way
!     (the "Module Docs" Start menu entry), make sure the "Start Browser"
!     button works, and make sure you can search for a random module (I
!     use "random" <wink>) and then that the "go to selected" button works.
!     It's amazing how much can go wrong here -- and even more amazing how
!     often last-second checkins break one of these things.  If you're "the
!     Windows geek", keep in mind that you're likely the only person
!     routinely testing on Windows, and that Windows is simply a mess.
  
!     Repeat all of the above on at least one flavor of Win9x, and one of
!     NT/2000.  On NT/2000, try both an Admin and a plain User (not Power
!     User) account.
  
!     WRT Step 5 above (verify the release media), since by the time release
!     files are ready to download I've generally run many Windows tests on
!     the installer I uploaded, I usually don't do anything for Step 5
!     except a full byte-comparison ("fc /b" if using a Windows shell) of
!     the downloaded file against the file I uploaded.
  
  
--- 523,561 ----
  Windows Notes
  
!     Windows has a GUI installer, various flavors of Windows have
!     "special limitations", and the Windows installer also packs
!     precompiled "foreign" binaries (Tcl/Tk, expat, etc).  So Windows
!     testing is tiresome but very necessary.
  
!     Concurrent with uploading the installer, Tim installs Python from
!     it twice: once into the default directory suggested by the
!     installer, and later into a directory with embedded spaces in its
!     name.  For each installation, he runs the full regression suite
!     from a DOS box, and both with and without -0.
  
!     He also tries *every* shortcut created under Start -> Menu -> the
!     Python group.  When trying IDLE this way, you need to verify that
!     Help -> Python Documentation works.  When trying pydoc this way
!     (the "Module Docs" Start menu entry), make sure the "Start
!     Browser" button works, and make sure you can search for a random
!     module (Tim uses "random" <wink>) and then that the "go to
!     selected" button works.
  
!     It's amazing how much can go wrong here -- and even more amazing
!     how often last-second checkins break one of these things.  If
!     you're "the Windows geek", keep in mind that you're likely the
!     only person routinely testing on Windows, and that Windows is
!     simply a mess.
! 
!     Repeat all of the above on at least one flavor of Win9x, and one
!     of NT/2000.  On NT/2000, try both an Admin and a plain User (not
!     Power User) account.
! 
!     WRT Step 5 above (verify the release media), since by the time
!     release files are ready to download Tim has generally run many
!     Windows tests on the installer he uploaded, he usually doesn't do
!     anything for Step 5 except a full byte-comparison ("fc /b" if
!     using a Windows shell) of the downloaded file against the file he
!     uploaded.