Nick Papior

> > But that is the same as the other arguments in the Section tuple, no? > > Yes, it's just that the more parameters you add, the worse it...

> Well in that case you might as well build the section yourself instead of passing a dict :) In any case I think it might be useful for some.

I don't know about this, @tfrederiksen what do you say?

> After talking with @tfrederiksen, I think the best way to go is to let users choose if they want the "supervised" version that makes sure you never leave dangling...

Great job @pfebrer. An idea, could we make the interface a bit more easy to use, something along the lines: ```python # create a class with only static members class...

> Yes, sure. I'm not sure how easy it is to explain to new python users the named tuple thing though. So they would probably just go with lists. But...

Also, why do you think your (old) approach is easier interactively? Having to count indices where to put in new items seems awfully hard to me?

You are absolutely right. Lets change it to then: ```python def heteroribbon(...): ... heteroribbon.Segment = namedtuple ``` ;) Still a function. :) As for the readability, `zip` is really easy...

> Good! Giving attributes to functions is accepted but nobody does it. This seems like a good case for it, I hope nobody gets mad laughing . Exactly, it has...

Now I just really want to clarify the units in #418, and then I really want it out. But after that, I should be able to do releases more often...