Dnia 2014-02-21, pią o godzinie 00:22 +0100, Matthias Klose pisze:
> Am 26.01.2014 19:59, schrieb Matthias Klose:
> > Python 3.4 beta2 is in testing, the python3-setuptools package is able to
> > handle
> > 3.4 builds. I am planning to go on with 3.4 as a supported Python 3 version
> > some time
Le 21/02/2014 22:28, Barry Warsaw a écrit :
> On Feb 21, 2014, at 12:22 AM, Matthias Klose wrote:
> +1 for automating it, and for the lintian warning. I think in general we
> should use /usr/bin/python3 or /usr/bin/python2 in shebang (I could accept
> /usr/bin/python for the latter, because as you
* Matthias Klose , 2014-02-21, 00:22:
The most common thing is a generated dependency on python3.x, because a
package contains a file/binary with a python3.x shebang. In most cases
this should be replaced with a python3 shebang, which can be done with
dh_python3 --shebang=/usr/bin/python3. But
On Feb 21, 2014, at 12:22 AM, Matthias Klose wrote:
>In most cases this should be replaced with a python3 shebang, which can be
>done with dh_python3 --shebang=/usr/bin/python3. But why not automate this?
>dh_python3 looks at the b-d's, and if it doesn't find a b-d on
>python3-all-dev or libpytho
Am 26.01.2014 19:59, schrieb Matthias Klose:
> Python 3.4 beta2 is in testing, the python3-setuptools package is able to
> handle
> 3.4 builds. I am planning to go on with 3.4 as a supported Python 3 version
> some time in February (targeting not later than Feb 9, release date of the
> first
> 3
On Sun, Jan 26, 2014 at 8:59 PM, Matthias Klose wrote:
> The 3.4 release is planned for March 16, so it shouldn't be too much of a
> surprise to make 3.4 the default for the next Debian release, and hopefully be
> able to drop 3.3.
\0/
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.de
6 matches
Mail list logo
