This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author skip.montanaro
Recipients skip.montanaro
Date 2008-12-08.01:22:49
SpamBayes Score 9.008146e-05
Marked as misclassified No
Message-id <18748.30438.749825.192737@montanaro-dyndns-org.local>
In-reply-to
Content
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.
History
Date User Action Args
2008-12-08 01:22:51skip.montanarosetrecipients: + skip.montanaro
2008-12-08 01:22:50skip.montanarolinkissue4587 messages
2008-12-08 01:22:49skip.montanarocreate