On Wed, Jun 1, 2011 at 5:26 PM, Ville M. Vainio <[email protected]> wrote:
> Lates one involves the new-ish (py 2.6) "namedtuple" structure which > is sort of "better Bunch". I have to admit I have mostly ignored it > previously, but perhaps not for long :). Imo, bunch does not need improving (but see below), and namedtuple is probably a step backward. Prohibiting leading underscores in keys is a bad hack, as is changing "improper" keys. For Leo, I would create real classes instead of g.bunch's, were I to write the code again. Performance is irrelevant for g.bunch in Leo, but the lack of real identity is a serious flaw in both bunches and tuples. That is, when I do repr(anObject), I want to know what that object *really* is. Just my opinion :-) Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" 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/leo-editor?hl=en.
