Re: Program shebang line with specific ‘/usr/bin/pythonX.Y’ interpreter (was: Bug#635476: current packaging work for Coverage)

2013-10-10 Thread Scott Kitterman
Ben Finney wrote: >Dmitry Shachnev writes: > >> In your particular case, python3-coverage depends on 'python3 (<< >> 3.4), python3 (>= 3.3)', so when it is installed /usr/bin/python3 >will >> be always a link to python3.3, so the shebang doesn't matter here. >But >> in general, I recommend peop

Re: Program shebang line with specific ‘/usr/bin/pythonX.Y’ interpreter (was: Bug#635476: current packaging work for Coverage)

2013-10-10 Thread Barry Warsaw
On Oct 10, 2013, at 10:04 PM, Ben Finney wrote: >I don't know the rationale for that dichotomy – only ‘/usr/bin/python’ >or ‘/usr/bin/pythonX.Y’ – but I also don't know why you recommend >against it. What is your reason for wanting that policy changed? It doesn't make sense to me to recommend /us

Program shebang line with specific ‘/usr/bin/pythonX.Y’ interpreter (was: Bug#635476: current packaging work for Coverage)

2013-10-10 Thread Ben Finney
Dmitry Shachnev writes: > In your particular case, python3-coverage depends on 'python3 (<< > 3.4), python3 (>= 3.3)', so when it is installed /usr/bin/python3 will > be always a link to python3.3, so the shebang doesn't matter here. But > in general, I recommend people to use non-versioned sheba

Re: Bug#635476: current packaging work for Coverage

2013-10-10 Thread Dmitry Shachnev
Hi Ben, and everybody. On Thu, Oct 10, 2013 at 12:15 PM, Ben Finney wrote: > On 09-Oct-2013, Dmitry Shachnev wrote: >> Then please make sure that shebang of "coverage3" is >> "#!/usr/bin/python3". > > I'm not doing anything specific to change the shebang line. That's being > done by the Debian Py