Documentation updates.

--HG--
branch : distribute
extra : rebase_source : ee1e27c3d9bb64e536b6f0c86d46d573db505b03

2 files changed, 12 insertions, 0 deletions

diff --git a/CHANGES.txt b/CHANGES.txt
index a08cba78..8fc1c3ff 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -7,6 +7,10 @@ CHANGES
 ------
 
 * Issue #283: Reenable scanning of *.pyc / *.pyo files on Python 3.3.
+* Issue #299: The develop command didn't work on Python 3, when using 2to3,
+  as the egg link would go to the Python 2 source. Linking to the 2to3'd code
+  in build/lib makes it work, although you will have to rebuild the module
+  before testing it.
 
 ------
 0.6.28
diff --git a/docs/setuptools.txt b/docs/setuptools.txt
index 4105dc2e..d04973e7 100644
--- a/docs/setuptools.txt
+++ b/docs/setuptools.txt
@@ -1082,6 +1082,14 @@ update the ``easy-install.pth`` file to include your project's source code,
 thereby making it available on ``sys.path`` for all programs using that Python
 installation.
 
+If you have enabled the ``use_2to3`` flag, then of course the ``.egg-link``
+will not link directly to your source code when run under Python 3, since
+that source code would be made for Python 2 and not work under Python 3.
+Instead the ``setup.py develop`` will build Python 3 code under the ``build``
+directory, and link there. This means that after doing code changes you will
+have to run ``setup.py build`` before these changes are picked up by your
+Python 3 installation.
+
 In addition, the ``develop`` command creates wrapper scripts in the target
 script directory that will run your in-development scripts after ensuring that
 all your ``install_requires`` packages are available on ``sys.path``.