On 2017-06-20 16:40:26 +0200 (+0200), Matthias Klose wrote:
[...]
> another one many openstack packages.
[...]
Spot checking the source packages in the archive currently, it looks
like Thomas already has most of these done.
By way of background there, a coordinated effort has been underway
for th
On 10.06.2017 05:32, Barry Warsaw wrote:
> On Jun 06, 2017, at 10:57 AM, Sandro Tosi wrote:
>
>> if we plan (and it looks like we do) to support and distribute 2.7
>> with buster, why not support it *properly*? what's the point of
>> deprecating python2.7? either we ship it or not, but if we do th
On Friday, June 09, 2017 08:32:38 PM Barry Warsaw wrote:
> On Jun 06, 2017, at 10:57 AM, Sandro Tosi wrote:
> >if we plan (and it looks like we do) to support and distribute 2.7
> >with buster, why not support it *properly*? what's the point of
> >deprecating python2.7? either we ship it or not, bu
On Jun 06, 2017, at 10:57 AM, Sandro Tosi wrote:
>if we plan (and it looks like we do) to support and distribute 2.7
>with buster, why not support it *properly*? what's the point of
>deprecating python2.7? either we ship it or not, but if we do then
>let's not cripple it by removing python2 module
> == Deprecate Python 2 ==
>
> Lintian checks for python 2 only packages
> Lintian checks for /usr/bin/python2? shebangs
please dont (as in "favor python3" but dont actively discourage
python2 development/packaging), see below
> == python 2.7s future ==
>
> Buster *may* be the last Debian release
5 matches
Mail list logo
