allow newer berkeley db versions

[doko42]

BPO	15235
Nosy	@doko42, @jcea

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = 'https://github.com/doko42'
closed_at = <Date 2013-03-20.00:11:45.794>
created_at = <Date 2012-07-01.08:36:07.890>
labels = ['build']
title = 'allow newer berkeley db versions'
updated_at = <Date 2013-03-20.00:11:45.793>
user = 'https://github.com/doko42'

bugs.python.org fields:

activity = <Date 2013-03-20.00:11:45.793>
actor = 'doko'
assignee = 'doko'
closed = True
closed_date = <Date 2013-03-20.00:11:45.794>
closer = 'doko'
components = ['Build']
creation = <Date 2012-07-01.08:36:07.890>
creator = 'doko'
dependencies = []
files = []
hgrepos = []
issue_num = 15235
keywords = []
message_count = 6.0
messages = ['164461', '164462', '164479', '164480', '164481', '184711']
nosy_count = 3.0
nosy_names = ['doko', 'jcea', 'python-dev']
pr_nums = []
priority = 'normal'
resolution = 'fixed'
stage = None
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue15235'
versions = ['Python 3.3']

[doko42]

setup.py still has a version check for berkley db, currently only allowing versions up to 5.1.x. I'm checking in a patch to bump this to allow versions up to 5.3.x.

Maybe this version check should be disabled (after 3.3), using berkley db as a backend for the dbm module doesn't rely on any fancy berkley db features.

[python-dev]

New changeset 7be082d80b8a by doko in branch 'default':

• Issue bpo-15235: Allow Berkley DB versions up to 5.3 to build the dbm module.
  http://hg.python.org/cpython/rev/7be082d80b8a

[jcea]

Mattias, the tracker indicates that PDF doesn't have your contributor agreement. Could you possibly send one?.

http://www.python.org/psf/contrib/contrib-form/

[jcea]

PDF = PSF (Python software Foundation)

[doko42]

hmm, that was submitted years ago ... (can we move this off line?)

[doko42]

fixed