[automated-testing] brickmux_ops issue
Vijay Bhaskar Reddy Avuthu
vavuthu at redhat.com
Mon Sep 3 10:47:26 UTC 2018
To avoid cyclic imports, One way I can think of is defer the import of
brick_libs at the beginning of the module.
Instead load the brick_libs when needed ( within the definition ).
On Fri, Aug 31, 2018 at 5:41 PM, Vitalii Koriakov <vkoriako at redhat.com>
> Hello guys.
> Faced such problem: we have 2 modules with circular import:
> brickmux_ops.py and brick_libs.py. They imports each other.
> So it need to be fixed in some way. I`v made temporary fixes where I
> disable a method which uses those import,
> but still we need to solve this, coz its architecture issue.
> Regards, Vitalii
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the automated-testing