Path: csiph.com!eternal-september.org!feeder.eternal-september.org!news.unit0.net!news.panservice.it!diesel.cu.mi.it!bofh.it!news.nic.it!robomod From: Ben Finney Newsgroups: linux.debian.maint.python Subject: Re: Package name for github.com/miguelgrinberg/python-socketio Date: Wed, 03 Aug 2016 01:30:01 +0200 Message-ID: References: X-Original-To: debian-python@lists.debian.org X-Mailbox-Line: From debian-python-request@lists.debian.org Tue Aug 2 23:27:54 2016 Old-Return-Path: X-Amavis-Spam-Status: No, score=-5.206 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, GMAIL=1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, LDO_WHITELIST=-5, RDNS_NONE=0.793] autolearn=no autolearn_force=no X-Policyd-Weight: using cached result; rate: -6.1 X-Greylist: delayed 903 seconds by postgrey-1.35 at bendel; Tue, 02 Aug 2016 23:27:38 UTC X-Injected-Via-Gmane: http://gmane.org/ Lines: 25 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit 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:I4jstYAt/UWikO6ZjCDDYrpnpEY= X-Mailing-List: archive/latest/14036 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/85mvku3gvd.fsf@benfinney.id.au Approved: robomod@news.nic.it Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Wed, 03 Aug 2016 09:12:22 +1000 X-Original-Message-ID: <85mvku3gvd.fsf@benfinney.id.au> X-Original-References: X-Original-X-Complaints-To: usenet@blaine.gmane.org Xref: csiph.com linux.debian.maint.python:8696 Luke Yeager writes: > The policy manual says the package name should be "python-socketio" > since I want to create a python2 package that provides the "socketio" > module. > > But that name is already taken by this project: > https://github.com/abourget/gevent-socketio Yes, this is a problem with the current Debian Python policy: it assumes distribution authors will not collide on package names. I don't have an answer, though I will point out that whatever the solution is, it will be incompatible with the current Debian Python policy for at least one of those packages. We need to discuss the problem and find a general solution that accepts the reality that upstream authors sometimes don't check whether the Python package name is already taken. -- \ “I was once walking through the forest alone and a tree fell | `\ right in front of me, and I didn't hear it.” —Steven Wright | _o__) | Ben Finney