Add a little more verbiage about the bsddb module/package change. It's

clear from recent discussions on c.l.py that people are a bit confused about
the differences between the old bsddb, the new bssdb, the bsddb3/PyBSDDB
package and changes to file formats.  Tried to clarify the issues.

diff --git a/Doc/whatsnew/whatsnew23.tex b/Doc/whatsnew/whatsnew23.tex
index f20c2084274b2b443b6c4bef18474cac09c305d5..80e829b0a47a59996d2faf0081b4e5be1d495f4b 100644 (file)
--- a/Doc/whatsnew/whatsnew23.tex
+++ b/Doc/whatsnew/whatsnew23.tex
@@ -1266,7 +1266,14 @@ The old version of the module has been renamed to
 have to edit \file{Modules/Setup} to enable it.  Note that the new
 \module{bsddb} package is intended to be compatible with the 
 old module, so be sure to file bugs if you discover any
-incompatibilities.
+incompatibilities.  When upgrading to Python 2.3, if you also change
+the underlying BerkeleyDB library, you will almost certainly have to
+convert your database files to the new version.  You can do this
+fairly easily with the new scripts \file{db2pickle.py} and
+\file{pickle2db.py} which you will find in the distribution's
+Tools/scripts directory.  If you've already been using the PyBSDDB
+package, importing it as \module{bsddb3}, you will have to change your
+\code{import} statements.
  
 \item The Distutils \class{Extension} class now supports
 an extra constructor argument named \var{depends} for listing