On 4 Feb 2005 04:01:25 -0800, rumours say that "Michele Simionato"
<[EMAIL PROTECTED]> might have written:
>I guess I need to add a os.link(src, dst) somewhere in the
>setup.py script or in a postinstallation script but I am not exactly
>sure where.
Since you want to make a symbolic link, you pro
On Fri, 04 Feb 2005 04:59:51 -0800, Michele Simionato wrote:
> Sylvain Thenault:
>> Actually it does install it is $PREFIX/bin.
>
> Aha! And how do I set $PREFIX? Is it a Unix environment variable or is it
> a keyword argument in setup? Something like setup( prefix="/usr") ?
it's a command line
Sylvain Thenault:
> Actually it does install it is $PREFIX/bin.
Aha! And how do I set $PREFIX? Is it a Unix environment variable or is
it
a keyword argument in setup? Something like setup( prefix="/usr") ?
--
http://mail.python.org/mailman/listinfo/python-list
On Fri, 04 Feb 2005 04:01:25 -0800, Michele Simionato wrote:
>>From what I see in the docs, registering a script just normalize the
> shebang line, but does not install it in /usr/bin, nor make any symbolic
> links, so it is not what I am looking for.
Actually it does install it is $PREFIX/bin.
>From what I see in the docs, registering a script just normalize the
shebang line, but does not install it in
/usr/bin, nor make any symbolic links, so it is not
what I am looking for.
I guess I need to add a os.link(src, dst) somewhere in the
setup.py script or in a postinstallation script but I
On Fri, 04 Feb 2005 02:45:34 -0800, Michele Simionato wrote:
> I want to distribute a pure Python package with this structure:
>
>>mypackage
>> __init__.py
>> module1.py
>> module2.py
>> ...
>> myexecutable.py
>
> In particular, myexecutable.py is a sc
I want to distribute a pure Python package with this structure:
>mypackage
> __init__.py
> module1.py
> module2.py
> ...
> myexecutable.py
In particular, myexecutable.py is a script which is intended to be used
from the command line via the shebang tric
