Re: [openstack-dev] [neutron][FWaaS] __init__ arguments issue status

nstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Subject: Re: [openstack-dev] [neutron][FWaaS] __init__ arguments issue status This break is almost certainly because of the following neutron change, to unwind the incestuous inheritance that was in neutron (dependency arrow was c

Re: [openstack-dev] [neutron][FWaaS] __init__ arguments issue status

This break is almost certainly because of the following neutron change, to unwind the incestuous inheritance that was in neutron (dependency arrow was circular): https://review.openstack.org/#/c/223343/ I don’t expect there will be a lot of appetite

Re: [openstack-dev] [neutron][FWaaS] __init__ arguments issue status

Hi Doug. The old and new MROs are both pretty complicated, and it’s not entirely clear to me yet why the original one worked. (The MROs are included below for reading pleasure; they're embellished to show the incoming args to self’s init and outgoing args to super’s init in each case.) I’m

Re: [openstack-dev] [neutron][FWaaS] __init__ arguments issue status

Excerpts from Nate Johnston's message of 2016-05-05 17:40:13 -0400: > FWaaS team, > > After a day of looking at the tests currently failing in the FWaaS repo, I > believe I have the issue narrowed down considerably. First, to restate what > is going on. If you check out the neutron-fwaas

[openstack-dev] [neutron][FWaaS] __init__ arguments issue status

FWaaS team, After a day of looking at the tests currently failing in the FWaaS repo, I believe I have the issue narrowed down considerably. First, to restate what is going on. If you check out the neutron-fwaas repository and run `tox -e py27` in it, you will get six errors all in the