Thanks for your advice, It's true that ImagePy is quickly hacked together and unprofessional(The main framework is build in 2 months). And that's why I didnot push it on pypi. I will so some clean up in 2018. But some different opinions:
1. about the "promotion" category, I think sometimes it is needed. Especially, I need to got more user, and some of them should be programer, when they use, they help me to do some test. I will test the interactive framework, but I have no time to test every algrithsm and function.
2. ImagePy's concept is borrow and integrate, the key is the interactive ui framework and the plugin system, not algrithsm. I wrote some in ipyalg, that's because something I must wrote:I found scikit-image's medial_axis function has some bug:https://github.com/scikit-image/scikit-image/issues/2550 the scikit-image's medial_axis make holes when thin. And sometimes we donot need many branch. So I wrote the check you saw.I need a skeleton analysis function, thanks for your skan, But I think a faster and a cleaner network is better, so I wrote it.eg: scikit-image's h_minima, h_maxima, watershed function is too slow, and when I process a large image, it would run death.so I wrote some function with numba. That's just temporary, I will replace with scikit-image's function when it's OK.
thanks for your advice, I will learn the PEP8 and numpy style.