Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.maint.python > #9560

Re: Ad-hoc Debian Python BoF at PyCon US 2017

Show all headers | View raw

> == 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 with Python 2.x. Maybe drop it into
> unstable-only, after that?
>
> Stefano is sceptical :P
>
> Fedora expects to be shipping 2.7 for a long while still.

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 modules packages. do yo think
that just because the module i want to use is not available will make
realize "oh sh*t, let's migrate this 50k lines of code application to
py3k so that i can implement this 5-minutes-of-work-funcionality if i
had the module on py2"?

the lintian check *currently* in place (discouraging to introduce py2
packages) is making more harm than good: it's easy to add a py2
package when you're packaging a new source module, it's a lot harder
(and impossible when you need that module in stable, unless you what
to use backports) once the package is already in the archive.

I'm happy that you work in a place where there are so few legacy
projects still on python2, and that you have some much time to migrate
them to py3k in a timely fashion; on the contrary, in many other
businesses, this is a long process, often requiring re-engineering and
a long trial-and-error phase to replace existing working py2 code with
py3k. Even more often, you just add functionalities to the old code
and move on to the next task: simply not providing py2 modules will
only frustrate our users (for example, me) and will force them to...
what's the solution here for a stable release? pip install the missing
deps? wow

sorry, just my 2c

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Ad-hoc Debian Python BoF at PyCon US 2017 Stefano Rivera <stefanor@debian.org> - 2017-05-25 02:30 +0200
  Re: Ad-hoc Debian Python BoF at PyCon US 2017 Sandro Tosi <morph@debian.org> - 2017-06-06 17:00 +0200
    Re: Ad-hoc Debian Python BoF at PyCon US 2017 Barry Warsaw <barry@debian.org> - 2017-06-10 05:40 +0200
      Re: Ad-hoc Debian Python BoF at PyCon US 2017 Scott Kitterman <debian@kitterman.com> - 2017-06-10 08:50 +0200
      Re: Ad-hoc Debian Python BoF at PyCon US 2017 Matthias Klose <doko@debian.org> - 2017-06-20 16:50 +0200
        Re: Ad-hoc Debian Python BoF at PyCon US 2017 Jeremy Stanley <fungi@yuggoth.org> - 2017-06-20 18:30 +0200

csiph-web