[Zope-CVS] CVS: Packages/WinBuilders/doc - ZC_PY_DIST_README.txt:1.5

[Tim Peters]

Update of /cvs-repository/Packages/WinBuilders/doc
In directory cvs.zope.org:/tmp/cvs-serv29908/doc

Modified Files:
	ZC_PY_DIST_README.txt 
Log Message:
Merging tim-zrs-branch back to the head.  This mainly introduces a
different way to build Python, + some new targets needed for ZRS.

- The python and zeo targets work fine, and also the new spread and
  spreadwrapper targets.  They even work fine on Win98SE, provided you
  don't use the native xcopy or xcopy32 (see README.txt for details).

- I had two problems with the zope target on Win98SE:

  + The Cygwin bash shell provokes a segfault in kernel32.dll when trying
    to run the synthesized .bat file that runs nmake.  I ran that makefile
    by hand from a regular DOS box instead, then reran the Zope buildout.

  + The Zope installer built by Inno Setup complains when it tries to
    extract bin\Lib\site-packages\formatter.py, claiming that the file
    is corrupted.  I can't see how this can be anything other than an
    Inno Setup bug:  Inno compressed this file itself, so if it can't
    extract it from the installer it builds, whose fault is that?
    Clicking the Ignore button worked fine, and Inno went on to install
    a working Zope.  This instance of formatter.py comes from win32all,
    and is used by PythonWin to drive the Scintilla text widget.  Zope
    doesn't need this.  Maybe this bug is specific to Win98SE; maybe
    not; beware!

- All the external extension modules that come with Python 2.3.3
  are included now (this includes bsddb, zlib, bz2, OpenSSL, and
  pyexpat).  It's no longer necessary to download the source for these.
  The inputs to the Python build process are now just python.org's source
  tarball + python.org's matching Windows installer.  The executables
  (.pyd, .dll, .exe) are extracted, pre-built, from the latter.  In fact,
  you don't even need a compiler anymore to run the Python part of the
  buildout.

  Since the Python buildout extracts all .pyds from the Windows installer,
  we'll automatically get all external extension modules that may be
  added in later Pythons.

  A less tangible benefit is that the python.org executables are much
  better tested than we can afford to do (exactly the same compiled files
  ship with Python 2.3.3 on Windows).

- For the zope and zeo targets, the build tree is cleaned up before
  building the installer:  embedded CVS directories are purged, and
  most text files (.py, .txt, .bat) are converted to have Windows
  line ends.  Since buildout extracts source mostly from Unix tarballs,
  most text files the installer pumped out were unintelligible using
  normal Windows tools (due to the Unix line ends).

- Targets that need to run Python now use the Python buildout from the
  build tree.  We weren't using that for anything before, except as input
  to Inno Setup, so the tree we put into the installer wasn't getting
  tested before (not even used).

- Assorted minor improvements to the buildout process.  It's still
  very complicated, alas.


=== Packages/WinBuilders/doc/ZC_PY_DIST_README.txt 1.4 => 1.5 ===
--- Packages/WinBuilders/doc/ZC_PY_DIST_README.txt:1.4	Fri Jan 30 22:16:52 2004
+++ Packages/WinBuilders/doc/ZC_PY_DIST_README.txt	Thu Feb  5 00:08:54 2004
@@ -3,9 +3,6 @@
 the Win32 Python version shipped with Zope and ZEO (the "ZC" version)
 and the version available from the Python.org website:
 
-- The ZC version builds pyexpat. [XXX But shouldn't -- all the expat code
-  is in the Python core starting with 2.3]
-
 - The ZC version does not write the same registry entries as the
   Python.org distribution.