[Py-howto-checkins] CVS: pyhowto python-2.0.tex,1.40,1.41

[A.M. K. <aku...@us...>]

Update of /cvsroot/py-howto/pyhowto
In directory slayer.i.sourceforge.net:/tmp/cvs-serv32595

Modified Files:
	python-2.0.tex 
Log Message:
Correction from David Bolen: the Windows version no longer crashes 
    on trying to import a 1.5 module
Bump the document version number


Index: python-2.0.tex
===================================================================
RCS file: /cvsroot/py-howto/pyhowto/python-2.0.tex,v
retrieving revision 1.40
retrieving revision 1.41
diff -C2 -r1.40 -r1.41
*** python-2.0.tex	2000/10/17 13:02:42	1.40
--- python-2.0.tex	2000/10/19 01:42:33	1.41
***************
*** 4,8 ****
  
  \title{What's New in Python 2.0}
! \release{1.00}
  \author{A.M. Kuchling and Moshe Zadka}
  \authoraddress{\email{am...@bi...}, \email{mo...@ma...} }
--- 4,8 ----
  
  \title{What's New in Python 2.0}
! \release{1.01}
  \author{A.M. Kuchling and Moshe Zadka}
  \authoraddress{\email{am...@bi...}, \email{mo...@ma...} }
***************
*** 832,845 ****
  The version number of the Python C API was incremented, so C
  extensions compiled for 1.5.2 must be recompiled in order to work with
! 2.0.  On Windows, attempting to import a third party extension built
! for Python 1.5.x usually results in an immediate crash; there's not
! much we can do about this.  (Here's Mark Hammond's explanation of the
! reasons for the crash.  The 1.5 module is linked against
! \file{Python15.dll}.  When \file{Python.exe} , linked against
! \file{Python16.dll}, starts up, it initializes the Python data
! structures in \file{Python16.dll}.  When Python then imports the
! module \file{foo.pyd} linked against \file{Python15.dll}, it
! immediately tries to call the functions in that DLL.  As Python has
! not been initialized in that DLL, the program immediately crashes.)
  
  Users of Jim Fulton's ExtensionClass module will be pleased to find
--- 832,838 ----
  The version number of the Python C API was incremented, so C
  extensions compiled for 1.5.2 must be recompiled in order to work with
! 2.0.  On Windows, it's not possible for Python 2.0 to import a third
! party extension built for Python 1.5.x due to how Windows DLLs work,
! so Python will raise an exception and the import will fail.
  
  Users of Jim Fulton's ExtensionClass module will be pleased to find
***************
*** 1335,1339 ****
  
  The authors would like to thank the following people for offering
! suggestions on drafts of this article: Mark Hammond, Gregg Hauser,
  Jeremy Hylton, Fredrik Lundh, Detlef Lannert, Aahz Maruch, Skip
  Montanaro, Vladimir Marangozov, Guido van Rossum, Neil Schemenauer,
--- 1328,1332 ----
  
  The authors would like to thank the following people for offering
! suggestions on various drafts of this article: David Bolen, Mark Hammond, Gregg Hauser,
  Jeremy Hylton, Fredrik Lundh, Detlef Lannert, Aahz Maruch, Skip
  Montanaro, Vladimir Marangozov, Guido van Rossum, Neil Schemenauer,