Missing Page/Bad Link & File on pipy for Installation

[GadgetSteve]

https://pypi.org/project/pyviz/ contains the text:

Installation

See pyviz.org (or doc/installation.rst for a github clone).

Which links to http://pyviz.org/installation.html and mentions doc/installation.rst - however both of these do not exist.

Suggest replacing the above with:
Installation

You can see all of the samples, etc. online at pyviz.org. If, however, you need a local copy simply clone or download from the github and follow the instructions in the README.md to run a local server.

Note that I would have submitted a PR but it seems that the above is not in the repository maybe one of the @pyviz-developers just needs to do a PyPi update to get the page re-generated.

[ceball]

Oh dear, sorry, that's confusing.

You are probably looking for https://pypi.org/project/holoviz/ - but please see http://blog.holoviz.org/pyviz-holoviz.html to check that...

[ceball]

@GadgetSteve Please could you say how you arrived at the pyviz package on pypi? I'm just wondering if there is a link somewhere still pointing to it that we need to update.

[ceball]

In any case, we should probably update the pyviz package on pypi to indicate it's deprecated in some way, and point people to holoviz, pyviz.org, etc.

I've lost track of how that kind of thing should be done on pypi now. Maybe we should at least just upload a new version that's the same as the old one, but with prominent notices in the README and maybe even a warning or similar on import?

[GadgetSteve]

@ceball I arrived at the pypi package from pyviz.org IIRC (there was a lot going on at the time).

If the package is deprecated then I think there is a meta-data mechanism for marking it as such. I think that the README.md in the github repository does not include these problems but could probably do with a depreciation notice and a pointer to holoviews being added.

I think that a part of the problem is that an update of the pip package hasn't been done so as to regenerate the page from the README.md - possibly because it is marked as build unknown on Travis & failing on Appveyor - or does this need to be done manually?