Message2711
I disagree with the "isn't a good idea" part.
While it's indeed not a good idea to use eval(repr(x)), it *is* a good idea to make repr(x) look like a syntactically correct expression that would recreate an object with the same value as x, given the appropriate environment (e.g. imported the class or factory function).
I hate non-standard object types whose repr() is indistinguishable from that of a similar standard object -- e.g. UserList makes this mistake, and xrange() used to pretend it was a tuple.
Nevertheless I'll try to think of something to add to the docs.
|
|
Date |
User |
Action |
Args |
2007-08-23 13:52:30 | admin | link | issue226264 messages |
2007-08-23 13:52:30 | admin | create | |
|