On Aug 5, 5:37 pm, Christopher Lee <[email protected]> wrote:
> Yuck. What a mess Python has inflicted on us: anydbm is supposed to
> provide a transparent interface to multiple backends, but even basic
> capabilities like iteration and __contains__ don't work for backends
> like gdbm and dbm.
In all fairness to Python I think iterators came after anydbm, and for
a long time they were not as commonly understood/used as they are
today.
I think it may better if the operations did not silently fall back to
some other backend - and then perform in an atrociously slowly.That
could just cause even more problems. The error message should be more
informative, and explicitly require bsddb.
> backends seem like throwbacks to the past. I believe Istvan looked at
> sqlite performance some time ago; I think it was pretty good.
Yes, I did, performance looked pretty good. And I think we could use
the code from
http://bugs.python.org/issue3783
right away, and update as necessary. Maybe this could be a independent
microrelease release after 0.8. that does not add any new
functionality but swaps out one backend for another. I can take a
second look in a few weeks (need to finish something else first, but
that will happen soon)
Istvan
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"pygr-dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/pygr-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
