> Maybe port to SQLite? I would not choose dbm these days. After sparring with it a while, I tweaked the existing job so that it chunked things into dbm-appropriate sizes to limp through; for the subsequent job (where I would have used dbm again) I went ahead and switched to sqlite and had no further issues.
I'm not sure if it's worth mentioning the issue in the docs for the dbm module so others don't bump against it. I'm not sure if the limit is on sum(size(key) for key in db) or the number of keys total. Just not the sort of thing I'd want someone to be depending on, unaware of the potential pitfalls. Thanks, -tkc -- https://mail.python.org/mailman/listinfo/python-list
