At 05:43 PM 9/3/2008 +0200, Hartmut Goebel wrote:
Phillip J. Eby schrieb:
> At 04:58 PM 9/3/2008 +0200, Hartmut Goebel wrote:
>> Hi,
>>
>> 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 :-)
So leave off the install-dir and script-dir arguments. By the way,
if you specify an install-dir, the script-dir defaults to that
directory, so your options are redundant anyway.
If your goal is simply to test scripts without affecting anything
else, the simple thing to do is:
python setup.py develop -md /some/dir
The -m means that /some/dir won't have to be on PYTHONPATH, and the
-d is short for --install-dir. You can then invoke
'/some/dir/myscript' to test. (Or if /some/dir is on your PATH, just
run 'myscript'.)
_______________________________________________
Distutils-SIG maillist - Distutils-SIG@python.org
http://mail.python.org/mailman/listinfo/distutils-sig
