BerkeleyDB 4.6.19 is a buggy release, the DB_HASH access method databases can lockup the process. This is why several of the bleeding edge distro buildbots are timing out while running test_bsddb3. I've created a simple C test case and made sleepycat^Woracle aware of the problem. I have a change in my sandbox to explicitly avoid linking with 4.6.19 but it seems like committing it would just pollute setup.py with vague notions of what versions of a specific library are bad. I'd prefer to just disallow use of libdb 4.6 completely in setup.py until oracle fixes this and we're sure no OS release ships with 4.6.19. thoughts? -gps http://groups.google.com/group/comp.databases.berkeley-db/browse_thread/thread/abf12452613ca7ec -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.python.org/pipermail/python-dev/attachments/20070909/6a2862d8/attachment.htm
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4