Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #12407
| Path | csiph.com!aioe.org!bofh.it!news.nic.it!robomod |
|---|---|
| From | Johannes Schauer <josch@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 15:40:02 +0200 |
| Message-ID | <zQ2NY-7sa-15@gated-at.bofh.it> (permalink) |
| References | <zQ21z-6WB-3@gated-at.bofh.it> |
| X-Original-To | Emilio Pozuelo Monfort <pochu@debian.org>, debian-devel <debian-devel@lists.debian.org> |
| X-Mailbox-Line | From debian-devel-request@lists.debian.org Mon Mar 30 13:30:24 2020 |
| Old-Return-Path | <josch@debian.org> |
| X-Amavis-Spam-Status | No, score=-11.725 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, KHOP_HELO_FCRDNS=0.275, LDO_WHITELIST=-5, PGPSIGNATURE=-5] autolearn=ham autolearn_force=no |
| X-Policyd-Weight | using cached result; rate: 0.5 |
| Content-Type | multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="===============0790708111687747532==" |
| MIME-Version | 1.0 |
| Content-Disposition | inline |
| Mail-Followup-To | Emilio Pozuelo Monfort <pochu@debian.org>, debian-devel <debian-devel@lists.debian.org>, debian-python@lists.debian.org |
| User-Agent | alot/0.9 |
| X-Mailing-List | <debian-devel@lists.debian.org> archive/latest/343436 |
| List-ID | <debian-devel.lists.debian.org> |
| List-URL | <https://lists.debian.org/debian-devel/> |
| List-Archive | https://lists.debian.org/msgid-search/158557500106.973286.5690503045836220592@hoothoot |
| Approved | robomod@news.nic.it |
| Lines | 83 |
| Organization | linux.* mail to news gateway |
| Sender | robomod@news.nic.it |
| X-Original-Cc | debian-python@lists.debian.org |
| X-Original-Date | Mon, 30 Mar 2020 15:30:01 +0200 |
| X-Original-Message-ID | <158557500106.973286.5690503045836220592@hoothoot> |
| X-Original-References | <3fed69b7-6801-a112-8c4b-e23a1b931fda@debian.org> |
| Xref | csiph.com linux.debian.devel:96043 linux.debian.maint.python:12407 |
Cross-posted to 2 groups.
Show key headers only | View raw
[Multipart message — attachments visible in raw view] - view raw
Hi, Quoting Emilio Pozuelo Monfort (2020-03-30 13:24:01) > We've just finished the transition to python3.8 as the default python3 > interpreter, which was a bit difficult due to some autopkgtest regressions in > a few rdeps, and to the fact that many modules only build their extensions > for the default python version, which means they have a strict dependency on > the python3 version[1] and they need to be rebuilt and migrated in lockstep > with python3-defaults. > > I have analyzed this based on current sid amd64 contents and have come up with > the following packages that don't ship extensions for both py3.7 and 3.8 (which > are the currently supported versions). Note that pure python packages that don't > build C extensions are not affected. > > It would be great if this situation can be improved in order to help with future > python transitions. Building for all the supported python versions can be done > by build-depending on python3-all-dev and compiling your package (or just the > python bits) with PYTHON pointing to each version. Depending on your package's > build system, this could be largely automated using some helper, such as > pybuild. If you don't know how to add support for your package, feel free to ask. 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? Could wrong build dependencies or binary packages which have a strict dependency on a python3 version not easily be detected by lintian? I'm not an expert in Python module packaging -- it just so happens that some packages I maintain offer Python bindings. Do you have a diff of a source package that successfully made the transition so that I know what I would have to change? 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? Thanks! cheers, josch
Back to linux.debian.maint.python | Previous | Next — Next in thread | Find similar | Unroll 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