search

networkx / networkx-metis

NetworkX Addon to allow graph partitioning with METIS
Other
79 stars 21 forks source link

Drop namespace packaging #36

Closed OrkoHunter closed 9 years ago

OrkoHunter commented 9 years ago

This PR removes all the dependency of networkx-metis on the namespace packaging and will live inside networx_metis-xxx.egg as a normal package.

This will obviously create two ways of using the library

from networkx.addons import metis
metis.partition()

and

import networkx_metis
networkx_metis.partition()

So, it's all upon the user to choose between the two methods. Kind of confusing though :(

Regarding .travis.yml, I've changed it to simply nosetests metis.tests.test_metis. We can easily change it when related changes are done in NetworkX core.

ysitu commented 9 years ago

Shall we make it concise and use nxmetis? A number of scikits packages are named skxxx.

OrkoHunter commented 9 years ago

I've been thinking for that too. In the beginning, when I used to test the package on my machine, I preferred naming the package as nxmetis.

ysitu commented 9 years ago

In .travis.yml, you do not need install a custom version of NetworkX anymore.

chebee7i commented 9 years ago

Why will it still be possible to do: from networkx.addons import metis? I was assuming networkx.addons would not exist at all.

OrkoHunter commented 9 years ago

Flask extensions should urge users to import from flask.ext.foo instead of flask_foo or flaskext_foo so that extensions can transition to the new package name without affecting users.

It's upon us how we want to present this addon.