[Python-Dev] _bsddb too unstable?
Jim Fulton
jim at zope.com
Wed Jul 14 13:07:06 CEST 2004
Gregory P. Smith wrote:
> On Tue, Jul 13, 2004 at 10:02:21AM -0400, Jim Fulton wrote:
>
>>I just wasted some time chasing down being unable to run the
>>Python test suite because the test_anydbm tests were segfaulting.
>>Removing the _bsddb module allowed the tests to run without
>>segfaulting.
>>
>>(FWIW, I'm running on Fedora Core 1, with db4-4.1.25-14)
>
>
> Where is the sf bugreport? what python cvs version/date was this,
> where did the segfault occur, what stack trace does the coredump show?
> test_anydbm.py with _bsddb using 4.1 or 4.2 do not coredump for me,
> if theres a bug i'd like to fix it.
Fair enough, I'll submit one.
>
>>I get the impression that this is a common problem.
>>Berkeley DB APIs often change in non-backward compatable
>>ways that cause this sort of problem. Perhaps these APIs
>>change too rapidly to allow the _bsddb extension to be included
>>in the distribution. I assume that this is the fault of
>>the Berkeley DB libraries, and not the extension, but I don't
>>really know. :/
>
>
> -1
>
> The Sleepycat BerkeleyDB API rarely changes.
This has not been my experience, but ...
> The extension is much
> more mutable as support for more of the sleepycat apis are added and
> enhancements are made to the compatibility interface, i'd expect this
> type of bug to be there first.
OK.
It sounds like you are very committed to making tis work. That
means a lot to me and is greatly appreciated.
Jim
--
Jim Fulton mailto:jim at zope.com Python Powered!
CTO (540) 361-1714 http://www.python.org
Zope Corporation http://www.zope.com http://www.zope.org
More information about the Python-Dev
mailing list