On Friday, March 04, 2011 08:06:55 pm Jakub Wilk wrote:
> * Piotr Ożarowski , 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 w
* Piotr Ożarowski , 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 you want to invoke
[Jakub Wilk, 2011-03-05]
> * Piotr Ożarowski , 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 in all ot
* Piotr Ożarowski , 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 "/usr/bin/python";
d
[Jakub Wilk, 2011-03-05]
> * Piotr Ożarowski , 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/b
* Piotr Ożarowski , 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 "/usr/bin/python";
d
"Piotr Ożarowski" 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, should options (-OO
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-packag
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?
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/python.'. This ensures that a
> Debian install
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
>
> how
On Fri, Mar 4, 2011 at 14:35, Scott Kitterman wrote:
> On Friday, March 04, 2011 08:30:02 am ProgVal wrote:
>> Hello,
>>
>> Python 2.7 is available in the Experimental repository, and I use it as the
>> default Python interpreter.
>> All modules and software I use works Python 2.7, but, modules an
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, this should only apply to *developer* packages, not operating system
On Fri, Mar 4, 2011 at 10:50 AM, Piotr Ożarowski wrote:
> [Tiago Saboga, 2011-03-04]
>> I'd like start helping the debian python community too. I wonder if
>> there is a list of help-needing packages, or recommendations for
>> beginners to help with debian python. I don't want to package new
>> mo
[Tiago Saboga, 2011-03-04]
> I'd like start helping the debian python community too. I wonder if
> there is a list of help-needing packages, or recommendations for
> beginners to help with debian python. I don't want to package new
> modules, as I see we already have some trouble with the existing
On Friday, March 04, 2011 08:30:02 am ProgVal wrote:
> Hello,
>
> Python 2.7 is available in the Experimental repository, and I use it as the
> default Python interpreter.
> All modules and software I use works Python 2.7, but, modules and libraries
> installed with aptitude are installed for Pyth
Hello,
Python 2.7 is available in the Experimental repository, and I use it as the
default Python interpreter.
All modules and software I use works Python 2.7, but, modules and libraries
installed with aptitude are installed for Python 2.6, and I have to update the
PYTHONPATH variable to use them.
Hi!
I'd like start helping the debian python community too. I wonder if
there is a list of help-needing packages, or recommendations for
beginners to help with debian python. I don't want to package new
modules, as I see we already have some trouble with the existing ones.
I don't mind triaging bu
[Tony Peña, 2011-03-01]
> hi, i wanna into the python modules team if is possible to help to Debian
> Project, and python comminity ,
could you start with sending me (or -team) patches (`svn diff > fix_foo.patch`)
first? I will then reply with a lot of questions/complains, so don't be
scared ;) -
19 matches
Mail list logo
