On December 22, 2016 2:33:23 AM EST, Diane Trout <di...@ghic.org> wrote: > >> This naming would be unacceptable. Python 3 package should be named >> as >> "python3-foobar", not "python-foobar". >> >> There are already packages called "python{,3}-pygraphviz" and you may >> want to >> take a look. > >The upstream source package name is graphviz and is hosted on pypi at >https://pypi.python.org/pypi/graphviz > >Obviously that conflicts with the original C language package grapvhiz, >so I thought python-graphviz was the best alternative. I'm open to >other suggestions. pypi-graphviz? > >The binary package name would be python3-graphviz. > >And yes there is a pygraphviz, but that's a different package with a >different API. > >But yes it is a bit silly there's so many different python graphviz >apis. > >I'm guessing the reason the dask developers used the pypi graphviz is >its pure python, unlike pygraphviz which is a C extension. But I'm not >sure, I just tried to use the task visulaization and got an import >error. > >dask uses the python graphviz library to generate plots like in this >notebook. >https://gist.github.com/mrocklin/b61f795004ec0a70e43de350e453e97e > >Diane
I think your original proposal is fine for the source package. Scott K