This is a very handy conversation... it coincides with work I'm doing quite nicely. On 7/8/05, Phillip J. Eby <pje@telecommunity.com> wrote:
FYI, --script-dir defaults to --install-dir if you explicitly set --install-dir, so the above could read:
python setup.py develop --install-dir=../buildutils -m
or for the ultimate in cryptic brevity:
python setup.py develop -md../buildutils
:)
This is a good trick. Unfortunately, it's not working for me. I have an egg installed for a package (A) that is required by a package (B) I'm working on. I wanted to debug something in A, so I upped the version number in A's setup script and ran the command you give up above. In the top level directory of project B, there is now an A.egg-link. Very cool. From that directory (and with that directory in sys.path), I was unable to find the newer version of A using pkg_resources.require. Removing the older egg from the easy-install.pth file fixed this problem... I was able to find the new version that was linked in just fine. This is with setuptools 0.5a8. As an aside, the thing that I'm trying to debug in A is a "Not a directory" error that I think is a __file__ usage. Ahh, the joys of being among the first to try to exploit this stuff. But I must say that, despite this, eggs are working great! Kevin