girder-client: Upload "latest" version to pypi

As of Sept 12th 2015, the latest girder-client documentation mentions that it could be installed using

pip install girder-client

This is not completely true, running this command will install version 1.0.2.

$ pip install girder_client
Collecting girder-client
[...]
Installing collected packages: girder-client
  Running setup.py install for girder-client
Successfully installed girder-client-1.0.2

This is a problem.

For example, the documentation mentions that the method listItem has the name parameter, but this has been added on Sept 4th in 66471e17 but version 1.0.2 has been uploaded on July 27th.

I would suggest that:

• the latest version is uploaded an pypi automatically each time a new commit is pushed on master. In that case, the documentation would specify pip install girder-client --pre. See here for the --pre option documentation.
• the vx.y.z documentation specifies pip install girder-client==vx.y.z

Cc: @girder/developers

[jcfr]

My proposal would be to publish to pypi only pre-release like this one (in addition of regular release):

And only publish these development packages as GitHub release assets:

Doing so would avoid uploading pypi with a lot of development packages while being a “good open-source citizen” (i think). Only “true” pre-release (marked as such with a tag) would be available on PyPi.

Only the latest development packages would be pushed as GitHub release assets.

[jcfr]

All of that said, this is a nitpick. It is great to see latest releases available 👍