Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit 959c772

Browse files
author
Skip Montanaro
committed
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.
1 parent ce6bf59 commit 959c772

1 file changed

Lines changed: 8 additions & 1 deletion

File tree

Doc/whatsnew/whatsnew23.tex

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1266,7 +1266,14 @@ \section{New, Improved, and Deprecated Modules}
12661266
have to edit \file{Modules/Setup} to enable it. Note that the new
12671267
\module{bsddb} package is intended to be compatible with the
12681268
old module, so be sure to file bugs if you discover any
1269-
incompatibilities.
1269+
incompatibilities. When upgrading to Python 2.3, if you also change
1270+
the underlying BerkeleyDB library, you will almost certainly have to
1271+
convert your database files to the new version. You can do this
1272+
fairly easily with the new scripts \file{db2pickle.py} and
1273+
\file{pickle2db.py} which you will find in the distribution's
1274+
Tools/scripts directory. If you've already been using the PyBSDDB
1275+
package, importing it as \module{bsddb3}, you will have to change your
1276+
\code{import} statements.
12701277

12711278
\item The Distutils \class{Extension} class now supports
12721279
an extra constructor argument named \var{depends} for listing

0 commit comments

Comments
 (0)