On 8/7/07, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote: > My concern is that people need to access existing databases. It's > all fine that the code accessing them breaks, and that they have > to actively port to Py3k. However, telling them that they have to > represent the keys in their dbm disk files in a different manner > might cause a revolt...
Too true. Offhand, why not provide hooks for serializing and deserializing keys? The same for values, too. People porting to py3k could use those. Besides, this thread makes it sound like people usually write their own wrapper classes whenever they use *dbm. Hooks would help with that, or even eliminate the need altogether. -j _______________________________________________ Python-3000 mailing list [email protected] http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
