fix README installation command and PyPI links

[ofek]

The current PyPI install command, links, and images point to the wrong package. I suppose this might be due to the new auto-generated documentation platform in use.

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed, please reply here (e.g. I signed it!) and we'll verify. Thanks.

---

• If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
• If you signed the CLA as a corporation, please let us know the company's name.

[ofek]

I've just signed the CLA.

[googlebot]

CLAs look good, thanks!

[dhermes]

Thanks for the PR but the change was intended. We are moving to google-cloud. See #1978 for context

[ofek]

@dhermes Ah, I see. Shouldn't we wait to update install command/links since, as of now, they are incorrect? This may confuse the product's users, especially the error-producing pip install google-cloud.

[dhermes]

Hopefully it will be transient, i.e. hopefully we have new versions ASAP

[tseaver]

We do need to publish a new version of the package Real Soon Now(TM). Likely a 0.19.0 version for the monolithic package, before we start pushing out releases for the API-specific sub-packages.

[tseaver]

@Ofekmeister Thanks for the patch~ I am closing the PR without merging., because as soon as we can get a release out, the links as they stand now (without your patch) will be correct.

[daspecster]

@tseaver, I'm reopening from #2298

[dhermes]

@Ofekmeister This looks mostly fine other than my comment about leaving --upgrade alone (instead of replacing it with -U). Also, this change is tiny, so can you squash into one commit?

$ git checkout master  # that is the name of your branch sent in this PR
$ git branch -m master master-old  # Renames the local master branch
$ git fetch upstream  # Make sure up to date
$ git branch master upstream/master  # Adds a tracking branch for the project's master
$ git checkout master
$ git merge --squash master-old
$ git diff origin/master  # Make sure the changes aren't too crazy.
$ git push --force origin master  # This will overwrite the extra commits in this PR

[tseaver]

@dhermes For a change this tiny, we could just squash merge it in the Github UI: I don't think we care about exposing it in a changelog.

[dhermes]

@tseaver Good call.

[ofek]

I believe I'm failing with git today. Can I just close this and open a new PR with all changes in one commit?

edit: git checkout master threw error: pathspec 'master' did not match any file(s) known to git.

[dhermes]

@Ofekmeister no worries, we can just use the GitHub squash merge feature on the PR. If you'd like to hone your git skills I'm happy to help you sort it out via Hangouts chat.

[ofek]

Yes, if you guys could please squash on your end that would be great.

@dhermes Thanks for the offer! That would be enlightening :) Based on search results, I believe it is a Windows issue.

[tseaver]

I cancelled the Travis build, as this PR only affects the README.