On Fri, Jan 30, 2009, Antoine Pitrou wrote: > Raymond Hettinger <python <at> rcn.com> writes: >> >> * If you're thinking that shelves have very few users and that >> 3.0.0 has had few adopters, doesn't that mitigate the effects >> of making a better format available in 3.0.1? Wouldn't this >> be the time to do it? > > There was already another proposal for an sqlite-based dbm module, you may > want to synchronize with it: > http://bugs.python.org/issue3783 > > As I see it, the problem with introducing it in 3.0.1 is that we would > be rushing in a new piece of code without much review or polish. Also, > there are only two release blockers left for 3.0.1, so we might just > finish those and release, then concentrate on 3.1.
There's absolutely no reason not to have a 3.0.2 before 3.1 comes out. You're probably right that what Raymond wants to is best not done for 3.0.1 -- but once we've agreed in principle that 3.0.x isn't a true production release of Python for PEP6 purposes, we can do "release early, release often". -- Aahz (a...@pythoncraft.com) <*> http://www.pythoncraft.com/ Weinberg's Second Law: If builders built buildings the way programmers wrote programs, then the first woodpecker that came along would destroy civilization. _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com