Hi Troy, All,
Thanks for this pointer. Yes I agree, there are constructs in here like the
subnet which can be leveraged by a L3 (forwarding) component implementation.
So just to build on this, and assuming that the IPAM component will be
integrated into Quantum (btw, is that already decided?),
So, there are mock adherents other than me. And apparently no strong voices
advocating for removal. Should it co-exist alongside mox then? Should there
be a preference as to how new tests are implemented? If replay is desired, mox
may still be useful, although my own experience suggests that
+1 to mock
On Thu, Apr 5, 2012 at 10:51 PM, Jason Kölker wrote:
> On Thu, 2012-04-05 at 20:04 -0700, Maru Newby wrote:
> > With that in mind, does anybody have any good arguments in favour of
> > keeping mock?
>
> PEP 417 - mock is in the stdlib as of Python 3.3.
>
> Happy Hacking!
>
> 7-11
>
>
3 matches
Mail list logo
