For those of you not following every bug in the SF tracker closely, in http://www.python.org/sf/775414 it's been suggested that the docs for 2.3.2 include a warning about using the old-style interface to bsddb (without a DBEnv) with multi-threaded applications. This seems like a prudent suggestion - does someone want to supply some words? Anthony
On Tue, Sep 30, 2003 at 12:45:05AM +1000, Anthony Baxter wrote:
For those of you not following every bug in the SF tracker closely, in http://www.python.org/sf/775414 it's been suggested that the docs for 2.3.2 include a warning about using the old-style interface to bsddb (without a DBEnv) with multi-threaded applications. This seems like a prudent suggestion - does someone want to supply some words?
Anthony
Attached is a patch. Commit it if you like it.
Looks good! I've upgraded it to a \begin{notice}[warning] so that it really stands out (see for instance http://www.python.org/doc/current/lib/node61.html ) Thanks! Anthony
Just another thought - should the newer pybsddb API be folded into the library docs? Anthony
On Wed, 2003-10-01 at 02:10, Anthony Baxter wrote:
Just another thought - should the newer pybsddb API be folded into the library docs?
They're big, but I think worth it. In general the pybsddb docs are excellent and invaluable, but I would make one change. I think the links to the C API point to pybsddb copies of the Sleepycat documentation. I'd change those to point to Sleepycat's own online documentation. It's more fragile, but 1) it means pulling less into Python's library, and 2) should be more up-to-date as Sleepycat makes changes and new releases. -Barry
On Wed, Oct 01, 2003 at 09:01:03AM -0400, Barry Warsaw wrote:
On Wed, 2003-10-01 at 02:10, Anthony Baxter wrote:
Just another thought - should the newer pybsddb API be folded into the library docs?
+1 all for it (for python 2.4). the pybsddb docs should be TeX-ified and included. They were originally written by Robin using a zope-ish formatted ascii -> html generator of some sort so automating the bulk of the task should be possible.
... but I would make one change. I think the links to the C API point to pybsddb copies of the Sleepycat documentation. I'd change those to point to Sleepycat's own online documentation. It's more fragile, but 1) it means pulling less into Python's library, and 2) should be more up-to-date as Sleepycat makes changes and new releases.
+1 agreed. One caveat: Sleepycat keeps the documentation for their current release of BerkeleyDB online at http://www.sleepycat.com/docs/. It doesn't mention any of the different behaviours or even API differences between it and older versions of BerkeleyDB. We have no way of knowing exactly what version the users python is compiled against other than in windows binary releases. Mentioning that caveat in the documentation should be enough. -g
participants (3)
-
Anthony Baxter -
Barry Warsaw -
Gregory P. Smith