New submission from Skip Montanaro <[EMAIL PROTECTED]>: Fixing issue4483 resulted in adding an extra header file check for gdbm-based header files when the gdbm library was found. This caused problems for Roumen Petrov. In considering the problems he encountered I decided we probably need to provide users some more flexibility when deciding which libraries and header files to use when building the dbm module (or _dbm on 3.0). For example, the current hard-coded perform checks in this order: ndbm, gdbm, BerkDB. What if the system has hdbm installed but the builder wants to use the BerkDB compatibility API?
This ticket is to track the discussion and come up with a suitable system. ---------- messages: 77280 nosy: skip.montanaro severity: normal status: open title: Need to rework the dbm lib/include selection process _______________________________________ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue4587> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
