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

Re: Python3 modules not built for all supported Python versions

Path	csiph.com!aioe.org!bofh.it!news.nic.it!robomod
From	Simon McVittie <smcv@debian.org>
Newsgroups	linux.debian.devel, linux.debian.maint.python
Subject	Re: Python3 modules not built for all supported Python versions
Date	Mon, 30 Mar 2020 16:10:01 +0200
Message-ID	<zQ3gZ-7SG-1@gated-at.bofh.it> (permalink)
References	<zQ21z-6WB-3@gated-at.bofh.it> <zQ2NY-7sa-15@gated-at.bofh.it>
X-Original-To	debian-devel@lists.debian.org
X-Mailbox-Line	From debian-devel-request@lists.debian.org Mon Mar 30 14:08:45 2020
Old-Return-Path	<smcv@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
MIME-Version	1.0
Content-Type	text/plain; charset=us-ascii
Content-Disposition	inline
X-Mailing-List	<debian-devel@lists.debian.org> archive/latest/343438
List-ID	<debian-devel.lists.debian.org>
List-URL	<https://lists.debian.org/debian-devel/>
List-Archive	https://lists.debian.org/msgid-search/20200330140829.GA673166@espresso.pseudorandom.co.uk
Approved	robomod@news.nic.it
Lines	32
Organization	linux.* mail to news gateway
Sender	robomod@news.nic.it
X-Original-Cc	Emilio Pozuelo Monfort <pochu@debian.org>, debian-python@lists.debian.org
X-Original-Date	Mon, 30 Mar 2020 15:08:29 +0100
X-Original-Message-ID	<20200330140829.GA673166@espresso.pseudorandom.co.uk>
X-Original-References	<3fed69b7-6801-a112-8c4b-e23a1b931fda@debian.org> <158557500106.973286.5690503045836220592@hoothoot>
Xref	csiph.com linux.debian.devel:96045 linux.debian.maint.python:12408

Cross-posted to 2 groups.

Show key headers only | View raw

On Mon, 30 Mar 2020 at 15:30:01 +0200, Johannes Schauer wrote:
> does this mean that build-depending on python3-dev is wrong in general and
> should instead be replaced by build-depending on python3-all-dev?

It is only wrong for packages that build Python 3 extensions (binary
modules) that are intended to be loadable by all supported Python
3 versions (roughly: `find /usr/lib/python3/dist-packages -name '*.so'`).

For packages that embed Python 3, like the versions of vim that
have Python scripting support, or packages that use a Python 3
extension as an internal implementation detail of some tool, like
gobject-introspection, my understanding is that build-depending
on python3-dev continues to be appropriate. These extensions would
ideally be installed in a private directory, like gobject-introspection's
/usr/lib/x86_64-linux-gnu/gobject-introspection/giscanner/_giscanner.cpython-38-x86_64-linux-gnu.so
- but I know some upstreams and some downstream maintainers (arguably
incorrectly) package private extensions as though they were public
extensions, because the mechanics of doing so are much simpler.

> For example the package src:ros-geometry2 has a super simple
> dh-style rules file, basically just doing:
> 
> %:
> 	dh $@ --buildsystem=cmake --with python3
> 
> What would I have to change to successfully fix this problem?

The general answer is that you would have to build it repeatedly in a
loop, with each supported version of Python 3 in turn. I am not aware
of a way to do this in a similarly simple rules file.

    smcv

Thread

Re: Python3 modules not built for all supported Python versions Johannes Schauer <josch@debian.org> - 2020-03-30 15:40 +0200
  Re: Python3 modules not built for all supported Python versions Simon McVittie <smcv@debian.org> - 2020-03-30 16:10 +0200
    Re: Python3 modules not built for all supported Python versions Piotr Ożarowski <piotr@debian.org> - 2020-03-30 21:00 +0200
    Re: Python3 modules not built for all supported Python versions Jochen Sprickerhof <jspricke@debian.org> - 2020-04-06 15:40 +0200

csiph-web