diff options
| author | mborch@valga.local <mborch@valga.local> | 2009-11-04 15:19:47 +0100 |
|---|---|---|
| committer | mborch@valga.local <mborch@valga.local> | 2009-11-04 15:19:47 +0100 |
| commit | 0118a1febd0bde436f3f0e392d016b8e7e7656c9 (patch) | |
| tree | b24676b3ed97a606f070425fd3915189f18d2ca0 | |
| parent | a2cf9c8a40e4e8d416ba976eb7a361d433586989 (diff) | |
| download | external_python_setuptools-0118a1febd0bde436f3f0e392d016b8e7e7656c9.tar.gz external_python_setuptools-0118a1febd0bde436f3f0e392d016b8e7e7656c9.tar.bz2 external_python_setuptools-0118a1febd0bde436f3f0e392d016b8e7e7656c9.zip | |
Copy change.
--HG--
branch : distribute
extra : rebase_source : b4f1e4c6288fe607310aabaf14ac508ad01c69a3
| -rwxr-xr-x | README.txt | 14 |
1 files changed, 8 insertions, 6 deletions
@@ -169,14 +169,16 @@ Another way is to add ``Distribute`` in the ``install_requires`` option:: Install FAQ ----------- -- **Why Distribute turn my Setuptools installation into an fake one?** +- **Why is Distribute wrapping my Setuptools installation?** - Since Distribute is a fork, and since it provides the same package and modules, - it fakes that the Setuptools installation is still present, so all the programs - that where using Setuptools still work. + Since Distribute is a fork, and since it provides the same package + and modules, it renames the existing Setuptools egg and inserts a + new one which merely wraps the Distribute code. This way, full + backwards compatibility is kept for packages which rely on the + Setuptools modules. - If it wasn't doing it, a program that would try to install Setuptools - would overwrite in turn Distribute. + At the same time, packages can meet their dependency on Setuptools + without actually installing it (which would disable Distribute). - **How does Distribute interact with virtualenv?** |