Nick Vatamaniuc a écrit :
(please don't top-post - corrected)
Bruno Desthuilliers wrote:
(snip)
A few observations and questions :
- you should avoid tests on concrete types as much as possible - at
least use isinstance
Good point about isinstance. Here is a good explanation why:
In message [EMAIL PROTECTED], Chris Spencer wrote:
I've been looking for a method of transparent, scalable, and
human-readable object persistence...
Don't do object persistence. What is an object? It's a combination of code
and data. Code structure is internal to your program--it has no
Chris Spencer wrote:
Before I get too carried away with something that's probably
unnecessary, please allow me to throw around some ideas. I've been
looking for a method of transparent, scalable, and human-readable object
persistence, and I've tried the standard lib's Shelve, Zope's ZODB,
Chris,
Interesting concept. But why is there a need for a human readable
object persistence that is x10 slower than pickle? In other words
present a good use case with a rationale (i.e. your criteria that you
mentioned). The only one I can think of so far is debugging.
Also some objects are
Good point about isinstance. Here is a good explanation why:
http://www.canonical.org/~kragen/isinstance/
Also the frozenset should be added the list of immutable types.
Nick Vatamaniuc
Bruno Desthuilliers wrote:
Chris Spencer wrote:
Before I get too carried away with something that's
Before I get too carried away with something that's probably
unnecessary, please allow me to throw around some ideas. I've been
looking for a method of transparent, scalable, and human-readable object
persistence, and I've tried the standard lib's Shelve, Zope's ZODB,
Divmod's Axiom, and
