Path: csiph.com!newsfeed.xs4all.nl!newsfeed7.news.xs4all.nl!news.uzoreto.com!aioe.org!bofh.it!news.nic.it!robomod
From: Andrey Rahmatullin <wrar@debian.org>
Newsgroups: linux.debian.maint.python
Subject: Re: help with FTBFS bug due to python3.8/3.9 confusion
Date: Mon, 26 Oct 2020 11:00:01 +0100
Message-ID: <B47sd-4GD-3@gated-at.bofh.it>
References: <B45A6-3xJ-3@gated-at.bofh.it>
Old-Return-Path: <wrar@debian.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="7AUc2qLy4jB3hD7Z"
Content-Disposition: inline
Approved: robomod@news.nic.it
Lines: 60
Organization: linux.* mail to news gateway
Sender: robomod@news.nic.it
Xref: csiph.com linux.debian.maint.python:12968


--7AUc2qLy4jB3hD7Z
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Oct 26, 2020 at 08:54:37AM +0100, Stephen Sinclair wrote:
> The recommendations are to change the build-dep on "python-dev" to
> "python-all-dev", and I can confirm that this does allow the package
> to build.  (Is this the right thing to do?)
Building a module for all supported Python versions is a right thing to
do.

> However, autopkgtest tests still fail.  The commenter in that bug
> report claims, "the lack of 3.8 modules in the package also explains
> your problem."  However, I do not understand that claim -- wouldn't it
> be counter-productive to specify which minor version of Python the
> package depends on?  I would need to update this manually when the
> default switches to Python 3.9.
If you are packaging a public module you need to provide it for all
supported Python versions.
Not sure which tests fail and how, I don't think this is described
anywhere?

> Although the CMake build is quite complicated and therefore I can
> expect such problems, but I am nonetheless confused why it would
> select the wrong Python version, as I do specify the Python executable
> via the command,
>=20
> > -DPYTHON_EXECUTABLE=3D$(shell which python3)"
>=20
> Is there a better way to find the path to the default python interpreter?
When building a public module you don't need to care about the default
version.

--=20
WBR, wRAR

--7AUc2qLy4jB3hD7Z
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQJhBAABCgBLFiEEolIP6gqGcKZh3YxVM2L3AxpJkuEFAl+WnZEtFIAAAAAAFQAP
cGthLWFkZHJlc3NAZ251cGcub3Jnd3JhckBkZWJpYW4ub3JnAAoJEDNi9wMaSZLh
/PMP/Rjlv2PeGHcqEl4JPzZ1FelRgq+bzqcgtLvFY4sOGEnh8gCrxgnqFjUlJodD
V4F3GxqaCxt86ltEzSTjKEPRB+B+O+bukq2BHTgnvrxisUQv21qPoAK5d6rvmK83
AqfWvGZucLM1tOhqgSieG13kdP0PYgjh9w7p6oYi13F5E1FVYtF36Hku2YP8p5Ch
rmqOqCvY4OkcG+8VF+p6khBODQL9a9cbWjWLaI29p2xctePquVb7DERxv+84+TKW
FXoU7iIVqSUrS+Mr7uk1rhTuaQoknbi+JHiXV295TxrIFcMXJLBBjPloRTvxjC+O
E1uR3zliPpPqXCCWYFqmP7WpTHX+UVH2BAmOW/ksnFUFONGDvX5Rws8s8xmJ8244
Lu6BROz910YddnyA8b4A3CcwX0E33HqT0Vyx2C7w1eleklx3mSiCQrKLQWjLnKKB
1tt4A64DON/XVl7dA+J2Vcj9kD/TqZxueuWKuHDehmhFBQk6vmaRWtTtVw4bLQGH
ozTThS1Dcf+G8BEylucqbkx8TmLRJ4j+1SpBUpJvSx9P2fvyctVe7S8bSFlSqRAu
MnmtpZtVh2XbMOon2EMgGl9FJ8PZhx4XTcedoWoPnlJ4TDAakLym7ZhiIKIwEta6
5CW9YOpUoJ10NALNYmddPMkM4Cay6oqUb7SOtLnEcKRP6mST
=vSoe
-----END PGP SIGNATURE-----

--7AUc2qLy4jB3hD7Z--