setup.py loads version information from VERSION

[rockobonaparte]

Previously, setup.py would import the version information from
pinject.version. This would trigger pinject's init.py to import and
load, which would take a roundabout path to importing the decorator
dependency. The setup.py script is launched by pip while inspecting the
package and dependencies, so this problem will come up in a package
sourcing pinject as a dependency even if decorator is declared as a
dependency in that package.

Referencing:
https://packaging.python.org/guides/single-sourcing-package-version/#single-sourcing-the-version

The previous method was similar to number 6 (setting the value of
version and then importing it). It was changed to number 4 (placing
the version in a VERSION file that is read from disk).

Given there is a parent VERSION file that is connected to the Makefile,
this file is now sourced by setup.py. To ensure it is available when
installing pinject, the VERSION file was also added to the manifest. The
existing version.py convention is kept for regular use by pinject since
that file is readily available to the package when running its source
normally.

This should fix issue #35.

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). 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 (or fixed any issues), please reply here (e.g. I signed it!) and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

[huan]

Thank you very much for your contribution!

Please:

1. Make sure all the CI passed and turned green, and
2. Make google bot happy

Then I will merge your PR after it gets at least one approvement from our contributors.

[rockobonaparte]

I signed it!

[googlebot]

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

[rockobonaparte]

The Travis CI failure was because it couldn't acquire Python 3.3 for Xenial (404 error trying to GET it). Can you check the environment? I don't think that's something I can mess with.

[huan]

@rockobonaparte Thanks for making the google bot happy!

Let's ignore the Python 3.3 failure from Travis, so your code looks good to me.

[rockobonaparte]

So who signs off now?

[rockobonaparte]

One-week anniversary! Do I need to do anything else?

[huan]

ping @trein

@rockobonaparte I would like to merge this PR if there are no change requests from other reviewers after 5.31

[huan]

Published to PyPI as v0.14.1

See: https://pypi.org/manage/project/pinject/release/0.14.1/