Wolodja Wentland writes:
> On Fri, Dec 04, 2009 at 19:34 -0500, Nikolaus Rath wrote:
>> All my Python files have extension .py. However, I would like to install
>> scripts that are meant to be called by the user without the suffix, i.e.
>> the file scripts/doit.py should end up as /usr/bin/doit.
>
Lie Ryan writes:
> On 12/5/2009 11:34 AM, Nikolaus Rath wrote:
>> Hello,
>>
>> All my Python files have extension .py. However, I would like to install
>> scripts that are meant to be called by the user without the suffix, i.e.
>> the file scripts/doit.py should end up as /usr/bin/doit.
>>
>> Appa
On Fri, Dec 04, 2009 at 19:34 -0500, Nikolaus Rath wrote:
> All my Python files have extension .py. However, I would like to install
> scripts that are meant to be called by the user without the suffix, i.e.
> the file scripts/doit.py should end up as /usr/bin/doit.
> Apparently the scripts= optio
On Dec 5, 1:52 am, Lie Ryan wrote:
> on linux/unix, you need to add the proper #! line to the top of any
> executable scripts and of course set the executable bit permission
> (chmod +x scriptname). In linux/unix there is no need to have the .py
> extension for a file to be recognized as python sc
On 12/5/2009 11:34 AM, Nikolaus Rath wrote:
Hello,
All my Python files have extension .py. However, I would like to install
scripts that are meant to be called by the user without the suffix, i.e.
the file scripts/doit.py should end up as /usr/bin/doit.
Apparently the scripts= option of the set
Hello,
All my Python files have extension .py. However, I would like to install
scripts that are meant to be called by the user without the suffix, i.e.
the file scripts/doit.py should end up as /usr/bin/doit.
Apparently the scripts= option of the setup() function does not support
this directly.
