diff options
| author | tarek <none@none> | 2009-12-12 13:16:12 +0100 |
|---|---|---|
| committer | tarek <none@none> | 2009-12-12 13:16:12 +0100 |
| commit | 4881ed310bd6d0c5fc361e882325c47dec7b8b3a (patch) | |
| tree | ba5d4b91178990159012704881d20517751913d9 | |
| parent | c0e0ad5b6e1df8a56d994d1033fd196ce2bfabac (diff) | |
| download | external_python_setuptools-4881ed310bd6d0c5fc361e882325c47dec7b8b3a.tar.gz external_python_setuptools-4881ed310bd6d0c5fc361e882325c47dec7b8b3a.tar.bz2 external_python_setuptools-4881ed310bd6d0c5fc361e882325c47dec7b8b3a.zip | |
fixed Rest :/0.6.9
--HG--
branch : distribute
extra : rebase_source : 63f5b734530917bd660799cbc567b3bec48bb5be
| -rwxr-xr-x | README.txt | 42 |
1 files changed, 18 insertions, 24 deletions
@@ -29,7 +29,7 @@ The fork has two goals: the same as for Python 2 code, but Distribute also helps you to support Python 2 and Python 3 from the same source code by letting you run 2to3 on the code as a part of the build process, by setting the keyword parameter - ``use_2to3`` to True. See http://packages.python.org/distribute for more + ``use_2to3`` to True. See http://packages.python.org/distribute for more information. - Refactoring the code, and releasing it in several distributions. @@ -45,7 +45,7 @@ More documentation ================== You can get more information in the Sphinx-based documentation, located -at http://packages.python.org/distribute. This documentation includes the old +at http://packages.python.org/distribute. This documentation includes the old Setuptools documentation that is slowly replaced, and brand new content. About the installation process @@ -117,7 +117,7 @@ Uninstallation Instructions --------------------------- Like other distutils-based distributions, Distribute doesn't provide an -uninstaller yet. It's all done manually! We are all waiting for PEP 376 +uninstaller yet. It's all done manually! We are all waiting for PEP 376 support in Python. Distribute is installed in three steps: @@ -150,36 +150,30 @@ Quick help for developers ------------------------- To create an egg which is compatible with Distribute, use the same -practice as with Setuptools, e.g.: +practice as with Setuptools, e.g.:: -{{{ -from setuptools import setup + from setuptools import setup -setup(... -) -}}} + setup(... + ) To use `pkg_resources` to access data files in the egg, you should -require the Setuptools distribution explicitly: +require the Setuptools distribution explicitly:: -{{{ -from setuptools import setup + from setuptools import setup -setup(... - install_requires=['setuptools'] -) -}}} + setup(... + install_requires=['setuptools'] + ) Only if you need Distribute-specific functionality should you depend -on it explicitly. In this case, replace the Setuptools dependency: +on it explicitly. In this case, replace the Setuptools dependency:: -{{{ -from setuptools import setup + from setuptools import setup -setup(... - install_requires=['distribute'] -) -}}} + setup(... + install_requires=['distribute'] + ) ----------- Install FAQ @@ -208,7 +202,7 @@ Install FAQ and if the virtualenv you are in was generated without the `--no-site-packages` option, the Distribute installation will stop. - You need in this case to build a virtualenv with the `--no-site-packages` + You need in this case to build a virtualenv with the `--no-site-packages` option or to install `Distribute` globally. - **How does Distribute interacts with zc.buildout?** |