[Barry Warsaw, 2012-04-25]
- dh_python{2,3} should rewrite the shebang lines by default, with an option
to disable that.
there wasn't a consensus so I dropped this idea, I think I will add it
as an optional feature in next upload, though.
--
Piotr Ożarowski Debian
On Apr 30, 2012, at 11:23 AM, Piotr Ożarowski wrote:
[Barry Warsaw, 2012-04-25]
- dh_python{2,3} should rewrite the shebang lines by default, with an option
to disable that.
there wasn't a consensus so I dropped this idea, I think I will add it
as an optional feature in next upload,
[Barry Warsaw, 2012-04-30]
On Apr 30, 2012, at 11:23 AM, Piotr Ożarowski wrote:
[Barry Warsaw, 2012-04-25]
- dh_python{2,3} should rewrite the shebang lines by default, with an
option
to disable that.
there wasn't a consensus so I dropped this idea, I think I will add it
as an
On Apr 30, 2012, at 05:00 PM, Piotr Ożarowski wrote:
I don't remember arguments against making it the default,
will have to dig the IRC/mailing list archives later.
I'd prefer rewrite since I think /usr/bin/env is almost always the wrong
thing to use in production (though I acknowledge Stefano's
Apologies for reviving this thread. It's recently come up in relation to
other discussions I've had and I did a grep over s/usr/bin to find instances
where /usr/bin/env python was being used. Stefano reminded me of this
thread, and when I went back and re-read it, I noticed there wasn't
[Jakub Wilk, 2011-03-05]
I'm not convinced it's only about getting rid of /usr/bin/env. Piotr
didn't give any rationale for the proposed changed and his algorithm (as
sorry, we talked about pytohn-dev thread on #debian-python and when I
saw Barry's mail on debian-python@ I just assumed
On Friday, March 04, 2011 01:23:40 pm Barry Warsaw wrote:
So I know many of you are on python-dev, so you might have seen this come
up, but traffic there can be pretty heavy at times.
Upstream Python recommends that the shebang line for scripts should be
#!/usr/bin/env python
however,
On Mar 04, 2011, at 02:15 PM, Scott Kitterman wrote:
Currently Python policy says:
1.4.2. Interpreter Location
---
The preferred specification for the Python interpreter is
`/usr/bin/python' or `/usr/bin/pythonX.Y'. This ensures that a
Debian installation
any objections to change all shebangs (that do not match
/usr/bin/python\d(\.\d+) but do math .+python.* regexp) to
/usr/bin/python¹ in dh_python2 and to /usr/bin/python3 in
dh_python3?
(+ an option to disable this behaviour in both helpers)
if yes, should options (-OO, etc.) be removed as well?
Hi Piotr (2011.03.05_00:23:46_+0200)
any objections to change all shebangs (that do not match
/usr/bin/python\d(\.\d+) but do math .+python.* regexp) to
/usr/bin/python¹ in dh_python2 and to /usr/bin/python3 in
dh_python3?
Grumble. I quite like being able to use light (not --no-site-packages)
Piotr Ożarowski pi...@debian.org wrote:
any objections to change all shebangs (that do not match
/usr/bin/python\d(\.\d+) but do math .+python.* regexp) to /usr/bin/python¹ in
dh_python2 and to /usr/bin/python3 in dh_python3? (+ an option to disable this
behaviour in both helpers) if yes,
* Piotr Ożarowski pi...@debian.org, 2011-03-04, 23:23:
any objections to change all shebangs (that do not match
/usr/bin/python\d(\.\d+) but do math .+python.* regexp) to
/usr/bin/python¹ in dh_python2 and to /usr/bin/python3 in
dh_python3?
dh_python2 would change /usr/bin/env python3 to
[Jakub Wilk, 2011-03-05]
* Piotr Ożarowski pi...@debian.org, 2011-03-04, 23:23:
any objections to change all shebangs (that do not match
/usr/bin/python\d(\.\d+) but do math .+python.* regexp) to
/usr/bin/python¹ in dh_python2 and to /usr/bin/python3 in
dh_python3?
dh_python2 would change
* Piotr Ożarowski pi...@debian.org, 2011-03-05, 01:20:
any objections to change all shebangs (that do not match
/usr/bin/python\d(\.\d+) but do math .+python.* regexp) to
/usr/bin/python¹ in dh_python2 and to /usr/bin/python3 in
dh_python3?
dh_python2 would change /usr/bin/env python3 to
[Jakub Wilk, 2011-03-05]
* Piotr Ożarowski pi...@debian.org, 2011-03-05, 01:20:
dh_python2 and dh_python3 cannot be used for the same files at the same
time (that's why dh_python2 igores python3-* packages, that's why
dh_python3 ignores python-* packages and that's why you have to use
-N/-p
* Piotr Ożarowski pi...@debian.org, 2011-03-05, 01:39:
dh_python2 and dh_python3 cannot be used for the same files at the
same time (that's why dh_python2 igores python3-* packages, that's
why dh_python3 ignores python-* packages and that's why you have to
use -N/-p in all other packages if
On Friday, March 04, 2011 08:06:55 pm Jakub Wilk wrote:
* Piotr Ożarowski pi...@debian.org, 2011-03-05, 01:39:
dh_python2 and dh_python3 cannot be used for the same files at the
same time (that's why dh_python2 igores python3-* packages, that's
why dh_python3 ignores python-* packages and
17 matches
Mail list logo
