This includes the changes sent in to travis-test branch by @chebee7i .
@ysitu I think I'm clear now about the presence of __init__.py in networkx/addons/metis/. It is necessary. See, networkx and networkx-metis are sharing the common namespace networkx.addons. So, in both the directories there should be an __init__.py containing the line
and nothing else. This establishes their relation of sharing a namespace. Any other package in future also needs the same configuration.
Now, if networkx and networkx-metis are both installed in the system, networkx.addons is a package but networkx.addons.metis is not because of the absence of __init__.py. So, that's why we need it.
I'll create a test branch shortly with current mastersetup and this fix_circular_import. We can try installing that branch.
This includes the changes sent in to
travis-testbranch by @chebee7i .@ysitu I think I'm clear now about the presence of
__init__.pyinnetworkx/addons/metis/. It is necessary. See, networkx and networkx-metis are sharing the common namespacenetworkx.addons. So, in both the directories there should be an__init__.pycontaining the lineand nothing else. This establishes their relation of sharing a namespace. Any other package in future also needs the same configuration.
Now, if
networkxandnetworkx-metisare both installed in the system,networkx.addonsis a package butnetworkx.addons.metisis not because of the absence of__init__.py. So, that's why we need it.I'll create a
testbranch shortly with currentmastersetupand thisfix_circular_import. We can try installing that branch.