Path: csiph.com!feeder.erje.net!2.eu.feeder.erje.net!newsfeed.datemas.de!weretis.net!feeder4.news.weretis.net!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod From: Thomas Goirand Newsgroups: linux.debian.maint.python Subject: Re: Updated PEP 394 (python and python2 commands) Date: Tue, 22 May 2018 21:00:01 +0200 Message-ID: References: X-Mailbox-Line: From debian-python-request@lists.debian.org Tue May 22 18:52:15 2018 Old-Return-Path: X-Amavis-Spam-Status: No, score=-7 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, LDO_WHITELIST=-5, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate: -5 Organization: Debian User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Mailing-List: archive/latest/15981 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/4a865bf1-b92b-f813-36bc-c919b7ff19d3@debian.org Approved: robomod@news.nic.it Lines: 57 Sender: robomod@news.nic.it X-Original-Date: Tue, 22 May 2018 20:51:54 +0200 X-Original-Message-ID: <4a865bf1-b92b-f813-36bc-c919b7ff19d3@debian.org> X-Original-References: <6dc7af52-174f-04c5-9149-cc5affa8afb1@debian.org> Xref: csiph.com linux.debian.maint.python:10575 On 05/17/2018 08:53 PM, Matthias Klose wrote: > 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. > > 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. 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. > > 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. > > The third step for buster+1 would be to drop the set of python* packages from > python-defaults. > > Both Debian 8 and Debian 9 already have the python2 symlink, so you could even > reuse binary packages in the older releases. If needed, python-defaults could > be packported to Debian 9 using versioned provides, and to Debian 8 introducing > the same set of python2 packages. > > Matthias Hi Matthias, We need to clear-out something. Is your proposal includes changing: "Build-Depends: python{,-all,-dev}" with: "Build-Depends: python2{,-all,-dev}" I don't think that's part of your proposal, but it looks like someone understood this, I'm not sure why. Cheers, Thomas Goirand (zigo)