Path: csiph.com!news.freedyn.net!aioe.org!bofh.it!news.nic.it!robomod From: Ben Finney Newsgroups: linux.debian.maint.python Subject: Re: pep8 renamed to pycodestyle Date: Tue, 21 Jun 2016 03:40:01 +0200 Message-ID: References: X-Original-To: debian-python@lists.debian.org X-Mailbox-Line: From debian-python-request@lists.debian.org Tue Jun 21 01:36:05 2016 Old-Return-Path: X-Amavis-Spam-Status: No, score=-9.125 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, HEADER_FROM_DIFFERENT_DOMAINS=0.001, LDO_WHITELIST=-5, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-1.426] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate: -6.1 X-Injected-Via-Gmane: http://gmane.org/ Lines: 52 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Gmane-NNTP-Posting-Host: jigong.madmonks.org User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.4 (gnu/linux) X-Public-Key-ID: 0xAC128405 X-Public-Key-Fingerprint: 517C F14B B2F3 98B0 CB35 4855 B8B2 4C06 AC12 8405 X-Public-Key-URL: http://www.benfinney.id.au/contact/bfinney-pubkey.asc X-Post-From: Ben Finney Cancel-Lock: sha1:QAw/sBV8SHFLE1kzXUSeVGnUydI= X-Mailing-List: archive/latest/13930 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/85mvmfxr1i.fsf@benfinney.id.au Approved: robomod@news.nic.it Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Tue, 21 Jun 2016 11:35:21 +1000 X-Original-Message-ID: <85mvmfxr1i.fsf@benfinney.id.au> X-Original-References: <20160620154937.2ecdfd4d@subdivisions.wooz.org> X-Original-X-Complaints-To: usenet@ger.gmane.org Xref: csiph.com linux.debian.maint.python:8598 Barry Warsaw writes: > You might be aware that the upstream pep8 package has been renamed to > pycodestyle. Both the command line and imports have changed, although > not in a backward compatible way unfortunately[1]. Ah, Python. We love you, but please grow a proper API versioning system :-/ > There's a new upstream flake8 which I'm preparing in git-dpm, but it > will be blocked until we decide what to do about the Debian pep8 > package. (I hope the upstream ‘flake8’ now defaults to conforming with PEP 8, instead of having default checks that contradict it.) > I think we eventually want to rename Source:pep8 to > Source:pycodestyle, as well as Package:pep8, Package:python-pep8, and > Package:python3-pep8. I suppose we could at least keep the source > package name unchanged and transition to the new binary package names. My understanding is that renaming a source package is rather more disruptive than renaming a binary package, is that right? If so, I would recommend: * Go ahead and transition the binary package names with the usual mechanisms : * Keep the old names as a transition package until after Debian Stretch is released. * Have the new binary packages declare Replaces and Conflicts relationships with the appropriate version specification of the old names. * Maybe even schedule the transition with the release team , to allow co-ordination of dependent packages. * Since you've determined the command-line interfaces are not compatible, the new commands should not be alternatives for the old. * As a separate matter, figure out how best to rename the source package to better correspond with the new name upstream. This could take an arbitrarily long time; IMO while it is desirable to rename the source package, there's no tearing need yet. -- \ “Come on, if your religion is so vulnerable that a little bit | `\ of disrespect is going to bring it down, it's not worth | _o__) believing in, frankly.” —Terry Gilliam, 2005-01-18 | Ben Finney