Re: make *.py +x

[Goswin von Brederlow <brederlo@informatik.uni-tuebingen.de>]

Ben Finney <ben@benfinney.id.au> writes:

> On 19-Oct-2005, Rakotomandimby Mihamina wrote:
>> I made my yum debian package, and when passing it to 'lintian -i',
>> It finds that many *.py files are not executable.
>
> This seems backwards.
>
> If a file is meant to be executable, the convention is to name it
> *without* a suffix (so that it can be executed as a command without
> needing to be aware of what language it's written in). This also means
> that it can be re-implemented in another language without changing the
> command interface.
>
> If it's to be included in other programs (primarily), the convention
> is to name it with a language-specific suffix and make it *not*
> executable. That's how I'd interpret *.py files.
>
> Why does lintian want to go against this convention?

Things in /usr/bin should be executable. Otherwise what is the point
of being there.

Things in /usr/lib/package (where *.py belongs) can be executable I
guess. I think lintian looks for the shebang line (#!....) and
anything with one is considered as should be executable.

MfG
        Goswin