Gah, that's right, I think we talked about that and I just forgot.  Looking
back over named.py, it seems like it'd be more consistent for me to also
apply that rule for name_order: when creating a test instance, populate it
with exactly the extensions desired *in the desired order* (if that matters
to your test).

I'll work on these couple of things and the factories for the last couple
of managers and get back to you.

thanks,
dan


On Sun, Oct 13, 2013 at 12:34 PM, Doug Hellmann <notifications@github.com>wrote:

> In stevedore/named.py:
>
> > +            used in ``names``.
> > +        :type name_order: bool
> > +        :param propagate_map_exceptions: Boolean controlling whether exceptions
> > +            are propagated up through the map call or whether they are logged
> > +            and then ignored
> > +        :type propagate_map_exceptions: bool
> > +        :return: The manager instance, initialized for testing
> > +
> > +        """
> > +
> > +        o = cls.__new__(cls)
> > +        o.namespace = 'TESTING'
> > +        o._names = names
> > +        o._name_order = name_order
> > +
> > +        # simulate excluding plugins not listed in names, which normally
>
> Do you think we need this step? I expected the test to populate the
> manager with exactly the extensions desired. Maybe I'm missing a use case/
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/dreamhost/stevedore/pull/29/files#r6934978>
> .
>