Thanks that's quite useful, I had never heard about these!

On Feb 11, 2014, at 8:22 AM, adamrp <notifications@github.com> wrote:

> In bipy/maths/stats/ordination/base.py:
> 
> > +
> > +
> > +class OrdinationResults(namedtuple('OrdinationResults',
> > +                                   ('eigvals', 'species', 'site', 'biplot',
> > +                                    'site_constraints'))):
> > +    __slots__ = ()  # To avoid creating a dict, as a namedtuple
> > +                    # doesn't have it
> > +
> > +    def __new__(cls, eigvals, species, site=None, biplot=None,
> > +                site_constraints=None):
> > +        return super(OrdinationResults, cls).__new__(cls, eigvals, species,
> > +                                                     site, biplot,
> > +                                                     site_constraints)
> > +
> > +
> > +class OrdinationResults2(namedtuple('OrdinationResults2',
> Pedantic curiosity led me to [this SO post]( http://stackoverflow.com/questions/9872255/when-and-why-should-i-use-a-namedtuple-instead-of-a-dictionary) after I began to wonder what advantages a list of ```namedtuples``` had over ```dict.items()```, just thought I'd share since others might be wondering the same thing :)
> …
> —
> Reply to this email directly or view it on GitHub.
>