Re: Bug#148415: jack: should use #!/usr/bin/python

2002-07-14 Thread Matthias Klose
reopen 148415
thanks

Chris Lawrence writes:
> On Jun 23, Michael Banck wrote:
> > Hi,
> > 
> > On Tue, May 28, 2002 at 05:22:32PM -0500, Chris Lawrence wrote:
> > > Some users may have a local version of Python installed (like Python
> > > >from CVS), so jack should use the path to the default Debian version
> > > of Python rather than using /usr/bin/env.

IMO Chris is right insisting on /usr/bin/python. We should make the
python policy more clear ...

> > 
> > As Python-policy says:
> > 
> > 1.3.2. Interpreter Location
> > 
> >  The preferred specification for the Python interpreter is
> >  `/usr/bin/python' or `/usr/bin/python.'.
> > 
> >  If a maintainer would like to provide the user with the possibility
> >  to override the Debian Python interpreter, he may want to use
> >  `/usr/bin/env python' or `/usr/bin/env pythonX.Y'.
> > 
> > I'll close this bug, OK?
> 
> Not OK, since the locally-installed Python may not/will not have
> access to jack's site-python files.  Using /usr/bin/env python is IMHO
> only acceptable if the package is self-contained or munges sys.path to
> include any non-standard modules in the search path.
> 
> 
> Chris
> -- 
> Chris Lawrence <[EMAIL PROTECTED]> - http://www.lordsutch.com/chris/
> 
> 
> -- 
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: Bug#148415: jack: should use #!/usr/bin/python

2002-06-25 Thread Michael Banck
Hi,

On Mon, Jun 24, 2002 at 10:00:38AM -0700, Sean 'Shaleh' Perry wrote:
> > Not OK, since the locally-installed Python may not/will not have
> > access to jack's site-python files.  Using /usr/bin/env python is IMHO
> > only acceptable if the package is self-contained or munges sys.path to
> > include any non-standard modules in the search path.
>  
> When packaging something for Debian, it is usually best to assume they are
> using Debian's packages.  If the user wants their own version of python, they
> can make a python package and install it instead of ours.

OK, thanks for the input.

 jack (2.99.8-4) unstable; urgency=low
 .
   * 05_she_bang_patch switched from #!/usr/bin/env python to
 #!/usr/bin/python (see: #148415)

I hope this is better?

Michael


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: Bug#148415: jack: should use #!/usr/bin/python

2002-06-24 Thread Sean 'Shaleh' Perry
> 
> Not OK, since the locally-installed Python may not/will not have
> access to jack's site-python files.  Using /usr/bin/env python is IMHO
> only acceptable if the package is self-contained or munges sys.path to
> include any non-standard modules in the search path.
> 

indeed.  If you have python in /opt/python/ and env can find it, none of the
Debian scripts will work because they do not know how to find their modules.

When packaging something for Debian, it is usually best to assume they are
using Debian's packages.  If the user wants their own version of python, they
can make a python package and install it instead of ours.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: Bug#148415: jack: should use #!/usr/bin/python

2002-06-23 Thread Chris Lawrence
On Jun 23, Michael Banck wrote:
> Hi,
> 
> On Tue, May 28, 2002 at 05:22:32PM -0500, Chris Lawrence wrote:
> > Some users may have a local version of Python installed (like Python
> > >from CVS), so jack should use the path to the default Debian version
> > of Python rather than using /usr/bin/env.
> 
> As Python-policy says:
> 
> 1.3.2. Interpreter Location
> 
>  The preferred specification for the Python interpreter is
>  `/usr/bin/python' or `/usr/bin/python.'.
> 
>  If a maintainer would like to provide the user with the possibility
>  to override the Debian Python interpreter, he may want to use
>  `/usr/bin/env python' or `/usr/bin/env pythonX.Y'.
> 
> I'll close this bug, OK?

Not OK, since the locally-installed Python may not/will not have
access to jack's site-python files.  Using /usr/bin/env python is IMHO
only acceptable if the package is self-contained or munges sys.path to
include any non-standard modules in the search path.


Chris
-- 
Chris Lawrence <[EMAIL PROTECTED]> - http://www.lordsutch.com/chris/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]