[Distutils] development-egg in current directory
tseaver at palladion.com
Wed Sep 3 18:07:38 CEST 2008
-----BEGIN PGP SIGNED MESSAGE-----
Hartmut Goebel wrote:
> Phillip J. Eby schrieb:
>> At 04:58 PM 9/3/2008 +0200, Hartmut Goebel wrote:
>>> I'm currently installing development eggs into the current directory
>>> (the checkout directory) like this:
>>> PYTHONPATH=.:$PYTHONPATH \
>>> python setup.py develop --install-dir . --script-dir .
>>> Since this has problems when re-running (see issue40), I wonder whether
>>> this is the correct use of the 'develop' egg. Any hints?
>> It's definitely not the correct use, especially since, depending on your
>> layout, it could potentially overwrite your scripts. develop is
>> intended for installing to a directory that's normally *already on*
>> sys.path. Why are you doing that?
> Because I defined script-entry-points which I need to test. If there is
> another way to so this, I'll happily change :-)
In such I case, I always create a virtualenv, and use *its* python to
do 'setup.py develop': the scripts are then installed into the 'bin'
directory of the virtualenv.
Tres Seaver +1 540-429-0999 tseaver at palladion.com
Palladion Software "Excellence by Design" http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
More information about the Distutils-SIG