❦ 2 avril 2017 10:21 +0100, Chris Lamb <lamby@debian.org> :
>> > On the current subject, I also agree we should not drop prematurely
>> > packages targeted to Python 2.
>
> The Lintian tag in question does not suggest maintainers should be
> removing existing Python 2 support from packages.
>
> It merely suggests that you should think twice before *adding* Python 2
> support when putting together a new package. Such support can always be
> added later after user demand. The idea is that if we never add such
> support we've not only saved ourselves some effort in the future, we've
> also encouraged the general adoption of Python 3.
>
> Perhaps this is not clear in the tag/warning/description? This appears to
> be a constant source of confusion/frustration, alas.
I don't want to second-guess too much what people may think about such a
tag but being in Lintian is a strong signal that it is OK to remove
Python 2 support from packages (new ones and by extension existing
ones). But, you are right, the Lintian tag doesn't say that.
I don't believe that a user of a Python 2 packages will think "Gosh!
I'll upgrade to Python 3 right away". I think it is more likely to think
"Those pesky Debian maintainers, always trying to force their
ways". Maybe this will encourage the general adoption of Python 3 a
bit. But maybe this will also encourage people to think that Debian is
not relevant for their needs.
When a package only exists for Python 3, asking for a Python 2 version
will lead to two outcomes:
1. You'll have to wait. Maybe a lot. But you'll get the package.
2. You may have to argue. You may get an answer that Python 2 is
deprecated and end of support is soon. Then, you may not get the
package.
For most source packages, adding a Python 2 package is dead easy.
--
Don't stop with your first draft.
- The Elements of Programming Style (Kernighan & Plauger)
Attachment:
signature.asc
Description: PGP signature