On 26 Dec 2015 12:55, "Jeremy Stanley" <fungi at yuggoth.org> wrote: > > Presumably we could rename our tox macro so that it doesn't shadow > the recently added tox builtin, but this problem will occur any time > support for another plugin is added which uses the same name as > something in our existing configuration so I'm not sure if there are > better options. > -- > Jeremy Stanley We could look to limit to a single warning? -- Darragh Bailey "Nothing is foolproof to a sufficiently talented fool" - unknown -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-infra/attachments/20151227/49d22aad/attachment.html>