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

Re: pep8 renamed to pycodestyle

Path	csiph.com!weretis.net!feeder4.news.weretis.net!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod
From	Thomas Goirand <zigo@debian.org>
Newsgroups	linux.debian.maint.python
Subject	Re: pep8 renamed to pycodestyle
Date	Tue, 21 Jun 2016 22:00:02 +0200
Message-ID	<rMA01-1Ki-1@gated-at.bofh.it> (permalink)
References	<rMdwt-44L-29@gated-at.bofh.it> <rMiPv-7uu-7@gated-at.bofh.it>
X-Mailbox-Line	From debian-python-request@lists.debian.org Tue Jun 21 19:51:25 2016
Old-Return-Path	<zigo@debian.org>
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
X-Enigmail-Draft-Status	N1110
Organization	Debian
User-Agent	Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Icedove/45.1.0
MIME-Version	1.0
Content-Type	text/plain; charset=utf-8
Content-Transfer-Encoding	quoted-printable
X-Mailing-List	<debian-python@lists.debian.org> archive/latest/13933
List-ID	<debian-python.lists.debian.org>
List-URL	<https://lists.debian.org/debian-python/>
List-Archive	https://lists.debian.org/msgid-search/5aaa0ec9-517d-3d86-9f0f-5a9833488194@debian.org
Approved	robomod@news.nic.it
Lines	24
Sender	robomod@news.nic.it
X-Original-Date	Tue, 21 Jun 2016 21:51:03 +0200
X-Original-Message-ID	<5aaa0ec9-517d-3d86-9f0f-5a9833488194@debian.org>
X-Original-References	<20160620154937.2ecdfd4d@subdivisions.wooz.org> <85mvmfxr1i.fsf@benfinney.id.au>
Xref	csiph.com linux.debian.maint.python:8601

Show key headers only | View raw

On 06/21/2016 03:35 AM, Ben Finney wrote:
> My understanding is that renaming a source package is rather more
> disruptive than renaming a binary package, is that right?

To my experience, renaming a source package is painless. The pain used
to be for FTP masters, but now even that is automated nowadays (with
their "clean cruft" script, whatever they called it...). I did rename
source packages like oslo-config -> python-oslo.config and
oslo.messaging -> python-oslo.messaging, just for the sake of
consistency. It was no problem at all, and when I contacted FTP masters,
they told me that nobody had anything to do to deal with it.

>   * Maybe even schedule the transition with the release team

We don't have enough of these in Python. More often than not, disruptive
uploads aren't coordinated, and it breaks the world.

Though in this case, since Barry is proposing hacks to support both
names (thanks, that's very much welcome!). So it will be smooth, and we
can slowly open, then close bugs, slowly.

Cheers,

Thomas Goirand (zigo)

Thread

pep8 renamed to pycodestyle Barry Warsaw <barry@debian.org> - 2016-06-20 22:00 +0200
  Re: pep8 renamed to pycodestyle Ben Finney <ben+debian@benfinney.id.au> - 2016-06-21 03:40 +0200
    Re: pep8 renamed to pycodestyle Thomas Goirand <zigo@debian.org> - 2016-06-21 22:00 +0200
  Re: pep8 renamed to pycodestyle Piotr Ożarowski <piotr@debian.org> - 2016-06-21 10:20 +0200
    Re: pep8 renamed to pycodestyle Barry Warsaw <barry@debian.org> - 2016-06-21 13:50 +0200
      Re: pep8 renamed to pycodestyle Ondrej Novy <novy@ondrej.org> - 2016-08-08 01:10 +0200
        Re: pep8 renamed to pycodestyle Barry Warsaw <barry@debian.org> - 2016-08-08 01:40 +0200
          Re: pep8 renamed to pycodestyle Ondrej Novy <novy@ondrej.org> - 2016-08-08 12:10 +0200
            Re: pep8 renamed to pycodestyle Barry Warsaw <barry@debian.org> - 2016-08-09 23:30 +0200

csiph-web