Path: csiph.com!news.samoylyk.net!gothmog.csi.it!bofh.it!news.nic.it!robomod From: Stefano Rivera Newsgroups: linux.debian.bugs.dist,linux.debian.maint.python Subject: Bug#791635: python-policy: Please require namespacing source python module packages Date: Wed, 23 Oct 2024 19:40:01 +0200 Message-ID: References: X-Original-To: Guillem Jover , Scott Kitterman , 791635@bugs.debian.org, Piotr Ozarowski , debian-python@lists.debian.org X-Mailbox-Line: From debian-bugs-dist-request@lists.debian.org Wed Oct 23 17:33:09 2024 Old-Return-Path: X-Spam-Flag: NO X-Spam-Score: 0.2 Reply-To: Stefano Rivera , 791635@bugs.debian.org Resent-To: debian-bugs-dist@lists.debian.org Resent-Cc: Matthias Klose X-Debian-Pr-Message: followup 791635 X-Debian-Pr-Package: python3 X-Debian-Pr-Keywords: wontfix X-Debian-Pr-Source: python3-defaults X-Gpg-Public-Key: http://www.rivera.za.net/stefano.gpg MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline User-Agent: NeoMutt/20220429 X-Greylist: delayed 460 seconds by postgrey-1.36 at buxtehude; Wed, 23 Oct 2024 17:30:13 UTC X-Debian-Message: from BTS X-Mailing-List: archive/latest/1864727 List-ID: List-URL: Approved: robomod@news.nic.it Lines: 34 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Wed, 23 Oct 2024 17:22:26 +0000 X-Original-Message-ID: <20241023172226.4us7tlthh5ozsncp@satie.tumbleweed.org.za> X-Original-References: <2309821.s1JQDg6CyC@localhost> <20230206142317.xdd7zx2ri2bic6g7@satie.tumbleweed.org.za> <20230129125209.k6yg664t66jyf7dq@sar0.p1otr.com> <20150707011106.GA12809@gaara.hadrons.org> Xref: csiph.com linux.debian.bugs.dist:1217679 linux.debian.maint.python:16398 Hi Guillem (2024.10.18_13:31:26_+0000) > > IMO source package names should follow upstream as closely as possible > > If Debian only contained python packages, that would make sense, > because python modules upstream need to care about not stomping over > each others names. But Debian contains source packages for multitude of > projects and language ecosystems, where their own modules can and do > share the same short and generic or conflicting module names with many > other language ecosystems modules (say json modules). These also can > conflict with command-line tools which use another common namespace, etc. > > Pretty much every other language specific team in Debian namespaces > their _source_ and _binary_ packages to avoid stomping/grabbing on > the global namespace. I don't really understand what makes python > special here, that it cannot follow a similar pattern. :/ It's worth drawing a distinction between libraries and apps here. I think it would be silly to namespace application source packages that are already installing a binary of that name. The fact that they are implemented in Python is hardly relevant. It's easier for everyone when the source and binary package names are the same, and match upstream's name. In general, namespacing libraries makes sense. Either with python- or whatever ecosystem they are part of. Stefano -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272