Path: csiph.com!aioe.org!bofh.it!news.nic.it!robomod From: Simon McVittie Newsgroups: linux.debian.maint.python,linux.debian.bugs.dist Subject: Re: Next python-mote pre-condition - issue with pybuild: python-backports.tempfile conflicting python-backports.weakref Date: Fri, 26 Jan 2018 01:50:02 +0100 Message-ID: References: X-Mailbox-Line: From debian-python-request@lists.debian.org Fri Jan 26 00:40:17 2018 Old-Return-Path: X-Amavis-Spam-Status: No, score=-7 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, LDO_WHITELIST=-5] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate: -5 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.9.2 (2017-12-15) X-Mailing-List: archive/latest/15482 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/20180126003952.GD25523@perpetual.pseudorandom.co.uk Approved: robomod@news.nic.it Lines: 23 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: Andreas Tille , debian-python@lists.debian.org, debian-science@lists.debian.org, 777089@bugs.debian.org, olivier.sallou@irisa.fr X-Original-Date: Fri, 26 Jan 2018 00:39:52 +0000 X-Original-Message-ID: <20180126003952.GD25523@perpetual.pseudorandom.co.uk> X-Original-References: <5a235cb3-46fb-8231-f3bf-5da74fe0f319@p10link.net> Xref: csiph.com linux.debian.maint.python:10087 linux.debian.bugs.dist:877740 On Thu, 25 Jan 2018 at 17:45:33 +0000, peter green wrote: > > However, in Debian case, I do not know how this can be handled as > > 2 packages cannot hold the same file (even if __init__ is only an empty > > file), and at least one must be present (if you install only one). The Python jargon is that the "backports" shared by backports.tempfile and backports.weakref is a "namespace package". For Python 2, dh_python2 handles this: python-lazr.restfulclient and python-lazr.uri are an example of cooperating packages that share a namespace package. For Python >= 3.3, the __init__.py is unnecessary due to . > I'm not a python expert but I expect the least-horrible way to do this > would be to ship a package that only contained the __init__. Then have > all the python-backports.* packages depend on it. This is not necessary, and would probably (hopefully?) lead to rejection from the NEW queue. smcv