On Wed, Aug 12, 2009 at 07:09:32PM -0700, Christopher Lee wrote: -> On Aug 7, 2009, at 5:58 AM, Istvan Albert wrote: -> -> > 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. -> -> I think your proposal is much more sensible than what I was -> suggesting. In the first 0.8 release, let's just raise a very clear -> error message if neither bsddb or gdbm (which we handle well) are -> available. Titus, what do you think?
Absolutely. -> >> 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) -> -> Yes, I think this is a great solution -- it genuinely solves the -> problem by providing a reliable backend. Yep -- let's put it on the list for 0.8.1. --t -- C. Titus Brown, [email protected] --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
