Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #10559
| Path | csiph.com!feeder.erje.net!2.eu.feeder.erje.net!news.roellig-ltd.de!open-news-network.org!weretis.net!feeder4.news.weretis.net!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod |
|---|---|
| From | Scott Kitterman <debian@kitterman.com> |
| Newsgroups | linux.debian.maint.python |
| Subject | Re: Updated PEP 394 (python and python2 commands) |
| Date | Fri, 18 May 2018 18:20:02 +0200 |
| Message-ID | <vQQgO-4Je-13@gated-at.bofh.it> (permalink) |
| References | <vQwi5-11b-1@gated-at.bofh.it> <vQJS2-Kf-25@gated-at.bofh.it> <vQPE5-4gw-9@gated-at.bofh.it> |
| X-Original-To | debian-python@lists.debian.org |
| X-Mailbox-Line | From debian-python-request@lists.debian.org Fri May 18 16:15:21 2018 |
| Old-Return-Path | <debian@kitterman.com> |
| X-Amavis-Spam-Status | No, score=-7.1 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, LDO_WHITELIST=-5] autolearn=ham autolearn_force=no |
| X-Policyd-Weight | DYN_NJABL=ERR(0) NOT_IN_SBL_XBL_SPAMHAUS=-1.5 NOT_IN_BL_NJABL=-1.5 CL_IP_EQ_HELO_IP=-2 (check from: .kitterman. - helo: .mailout03.controlledmail. - helo-domain: .controlledmail.) FROM/MX_MATCHES_NOT_HELO(DOMAIN)=0; rate: -5 |
| Dkim-Signature | v=1; a=ed25519-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201803e; t=1526660093; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from : subject : date; bh=kjNdHFiEiro8Zh0/fIc130M3sAj64sEm/ZBBi7mpe8M=; b=1LVQvlK9ygS8U3jo98c+SutjWJtN9uLTOnyx+g36i3HSNgECfHEXSTaK qbLdfPWXw3LgW++L8ejafGtCKqAnAA== |
| Dkim-Signature | v=1; a=rsa-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201803r; t=1526660093; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from : subject : date; bh=kjNdHFiEiro8Zh0/fIc130M3sAj64sEm/ZBBi7mpe8M=; b=DAkYIFSin9lVWgu+a0C0vAxy7xqZ2lpmQxLIZHmHW2PFkDIm2ZOcvkG8 6ydP02baHV3PfdqslSb6t13jsPs2Zwm6Qb/z0zxiWJnzXt64qCcaOrDQls iDT/pIwNHNGdpi/iKfdYpycoKJhn1Vh+1lkYECtzG6PZjoUVT1HZ31nOqv 7/lFJNM4ov2Z4hUOPa5GXbCD2F3TzYCGUT1SuC3LV8JN5U57rbmI6nVIHP afz3WSusSgoXAaQRasvBJmPvdbCxQ63UkdbAKK375K9LleZxIRKyVvmqTy MjdrUtWt3F6IWONUuy9+ujPUHQuUd7vnBGCjNyJLVaYjS0gicwPWNg== |
| User-Agent | KMail/4.13.3 (Linux/3.13.0-147-generic; KDE/4.13.3; x86_64; ; ) |
| MIME-Version | 1.0 |
| Content-Transfer-Encoding | quoted-printable |
| Content-Type | text/plain; charset="utf-8" |
| X-Mailing-List | <debian-python@lists.debian.org> archive/latest/15964 |
| List-ID | <debian-python.lists.debian.org> |
| List-URL | <https://lists.debian.org/debian-python/> |
| List-Archive | https://lists.debian.org/msgid-search/1820251.d4O7StkOgF@kitterma-e6430 |
| Approved | robomod@news.nic.it |
| Lines | 107 |
| Organization | linux.* mail to news gateway |
| Sender | robomod@news.nic.it |
| X-Original-Date | Fri, 18 May 2018 12:14:53 -0400 |
| X-Original-Message-ID | <1820251.d4O7StkOgF@kitterma-e6430> |
| X-Original-References | <6dc7af52-174f-04c5-9149-cc5affa8afb1@debian.org> <20180518091951.jk6gvppn7yxyx5zp@sar0.p1otr.com> <2129b34f-a837-2d14-4400-3fa44785885d@debian.org> |
| Xref | csiph.com linux.debian.maint.python:10559 |
Show key headers only | View raw
On Friday, May 18, 2018 11:31:37 AM Matthias Klose wrote: > On 18.05.2018 05:19, Piotr Ożarowski wrote: > > [Matthias Klose, 2018-05-17] > > > >> PEP 394 [1] saw an update in April 2018 [2], the diffs at [3]. > >> > >> The most important change from my point of view is > >> > >> -* It is suggested that even distribution-specific packages follow the > >> - ``python2``/``python3`` convention, even in code that is not intended > >> to > >> +* It is strongly encouraged that distribution-specific packages use > >> ``python2`` + or ``python3`` rather than ``python``, even in code that > >> is not intended to>> > >> operate on other distributions. > > > > FTR: the day this PEP asks us to point /usr/bin/python to python3 is the > > day I start ignoring it, to say the least. > > > >> I don't think there is enough time to replace all python shebangs to > >> python2 in time for the buster release, however there is no harm in > >> starting this process now. > > > > too late, this process has already started (since dh_python2 v3.20180313) > > ;-P> > >> But I'd like to get this done for buster+1, in the case we still need to > >> ship a Python2/2.7, so that buster+1 doesn't ship with a python command, > >> but maybe with a python2 command. > > > > we already ship /usr/bin/python2. Removing /usr/bin/python makes sense > > as well (administrators can symlink it to whatever they want once it's > > gone from Debian), but... > > > >> The first step is to create a set of python2* packages in > >> python-defaults, with contain all the python2* symlinks, and having the > >> python* packages depend on those python2 packages. This change itself > >> is a no-op and shouldn't affect anything. > >> > >> As a second step change the dh_python2 (in python-defaults), and > >> dh-python to generate dependencies on python2 instead of python, and > >> replacing the shebang from python to python2. > >> > >> This should cover the majority of packages to replace dependencies on > >> python with dependencies on python2. There are packages which don't > >> check for python2, so these probably need adjustments. But again, the > >> goal for buster+1 is to ship as few Python2 dependent packages as > >> possible, if any. > > > > this is useless. What will we gain by renaming packages? > > who said, that we should rename packages? The only packages being dropped > are the python defaults packages. > > > I refuse to do that work! > > There is no work in renaming the packages. It's about the dependency > generation and the shebang. > > > The only message it sends is that we don't think /usr/bin/python or > > python package is Python 2.7 anymore and that's definitely not the > > message I want to send. > > No, that's not what the PEP says. Upstream is free to follow Arch in their insanity (even if more slowly) and suggest pointing /usr/bin/python at a python3 version is a reasonable thing to do (eventually). It's not (and they even explain why in the PEP). Debian doesn't have to follow. We can have higher standards. I don't see any reason to be able to "apt install python2" instead of "apt install python". I think it's perfectly fine the way it is now where the same package provides /usr/bin/oython and /usr/bin/python2. If you exclude eventually pointint /usr/bin/python at a python3 version (and we should), then there's no value in doing it. I agree with Piotr. I don't think we need to "create a set of python2* packages". Scott K
Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Updated PEP 394 (python and python2 commands) Matthias Klose <doko@debian.org> - 2018-05-17 21:00 +0200
Re: Updated PEP 394 (python and python2 commands) Piotr Ożarowski <piotr@debian.org> - 2018-05-18 11:30 +0200
Re: Updated PEP 394 (python and python2 commands) Matthias Klose <doko@debian.org> - 2018-05-18 17:40 +0200
Re: Updated PEP 394 (python and python2 commands) Scott Kitterman <debian@kitterman.com> - 2018-05-18 18:20 +0200
Re: Updated PEP 394 (python and python2 commands) Matthias Klose <doko@debian.org> - 2018-05-18 19:40 +0200
Re: Updated PEP 394 (python and python2 commands) Scott Kitterman <debian@kitterman.com> - 2018-05-18 21:20 +0200
Re: Updated PEP 394 (python and python2 commands) Piotr Ożarowski <piotr@debian.org> - 2018-05-18 19:10 +0200
Re: Updated PEP 394 (python and python2 commands) Matthias Klose <doko@debian.org> - 2018-05-18 19:20 +0200
Re: Updated PEP 394 (python and python2 commands) Piotr Ożarowski <piotr@debian.org> - 2018-05-18 19:30 +0200
Re: Updated PEP 394 (python and python2 commands) Matthias Klose <doko@debian.org> - 2018-05-18 19:40 +0200
Re: Updated PEP 394 (python and python2 commands) Stuart Prescott <stuart@debian.org> - 2018-05-19 07:30 +0200
Re: Updated PEP 394 (python and python2 commands) Matthias Klose <doko@debian.org> - 2018-06-08 19:10 +0200
Re: Updated PEP 394 (python and python2 commands) Piotr Ożarowski <piotr@debian.org> - 2018-06-10 14:00 +0200
Re: Updated PEP 394 (python and python2 commands) Matthias Klose <doko@debian.org> - 2018-09-25 21:40 +0200
Re: Updated PEP 394 (python and python2 commands) Piotr Ożarowski <piotr@debian.org> - 2018-09-25 23:20 +0200
Re: Updated PEP 394 (python and python2 commands) Thomas Goirand <zigo@debian.org> - 2018-05-20 23:50 +0200
Re: Updated PEP 394 (python and python2 commands) Scott Kitterman <debian@kitterman.com> - 2018-05-21 01:40 +0200
Re: Updated PEP 394 (python and python2 commands) Thomas Goirand <zigo@debian.org> - 2018-05-22 09:10 +0200
Re: Updated PEP 394 (python and python2 commands) Thomas Goirand <zigo@debian.org> - 2018-05-22 21:30 +0200
Re: Updated PEP 394 (python and python2 commands) Scott Kitterman <debian@kitterman.com> - 2018-05-23 02:10 +0200
Re: Updated PEP 394 (python and python2 commands) Thomas Goirand <zigo@debian.org> - 2018-05-22 21:00 +0200
csiph-web