Initial checkout of setuptools depends on egg-info

[ghost]

Originally reported by: jaraco (Bitbucket: jaraco, GitHub: jaraco)

---

In Pull Request #94 and Pull Request #101, Marc is working on a technique to address the issue that the egg-info is present in the repo, so subtle changes to the environment (such as Python version) can cause those files to be modified.

The reason the files in the current implementation are modified is because they can actually change. For example, when six was added as a dependency in the (yet unreleased) fix for #229, the egg-info changed: 5cb125f2eaf3. So while this Pull Request #101 prevents egg-info from being re-written, it doesn't provide a way for the egg-info to be updated when it's actually necessary.

I think now that setuptools is on a stable Python 3 compatible code base, many of the issues around the in-repo egg-info may have subsided.

Ideally, the solution should involve allowing setuptools to bootstrap itself from a fresh checkout, by allowing egg_info to be invoked from a fresh checkout. It shouldn't need to keep a copy in the repo.

It seems setuptools at one time supported bootstrapping from a fresh checkout.

---

• Bitbucket: https://bitbucket.org/pypa/setuptools/issue/278

[ghost]

Original comment by jaraco (Bitbucket: jaraco, GitHub: jaraco):

---

Adding 'bootstrap.py' for bootstrapping a development environment when setuptools metadata isn't already present. Fixes #278.