Path: csiph.com!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod From: Piotr =?utf-8?Q?O=C5=BCarowski?= Newsgroups: linux.debian.devel,linux.debian.maint.python Subject: Re: Python3 modules not built for all supported Python versions Date: Mon, 30 Mar 2020 21:00:02 +0200 Message-ID: References: X-Original-To: debian-devel@lists.debian.org, debian-python@lists.debian.org X-Mailbox-Line: From debian-devel-request@lists.debian.org Mon Mar 30 18:59:36 2020 Old-Return-Path: X-Amavis-Spam-Status: No, score=-6.85 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_EF=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, LDO_WHITELIST=-5, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate: -4.6 X-Greylist: delayed 460 seconds by postgrey-1.36 at bendel; Mon, 30 Mar 2020 18:59:23 UTC Dkim-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ozarowski.pl; h= content-transfer-encoding:user-agent:in-reply-to :content-disposition:content-type:content-type:mime-version :references:message-id:subject:subject:from:from:date:date :received:received; s=default; t=1585594298; x=1587408699; bh=I2 oDt22BEZlXuMTA9anVoEQSKPUw2VlLKcyas6DoMpk=; b=QVoiIhq4BeAfBh9Gt6 z6vwzd3vJanEUpJdqHY6PjAiYLcHTPDbXiVgrVSp0XfNeZUxyTYO9Ffno7IrFsmD +wXSET2Y5gv7PQPO8BRaDR/v0vxH6Pf+cLSsARICGWNc1vUBJgHyDtnS/7H5ER+W obfAw1Hsa6tUhncluwn29YhGoOIifx6JA7KekA29Nr8dSQwc5u6AHsMeQL2rX4Kb HHOPffTisbv8F96neQSM1OONC5f2wZTw2WzqUwzm+/enlydvKXQanlp3yMyiVwLe it+g8kJckv2TwcXCDCq9bQNIDfMias000XT3s9UQOQe/j1y8F1MjorXaHE8D54G6 5Whg== Mail-Followup-To: debian-devel@lists.debian.org, debian-python@lists.debian.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline User-Agent: NeoMutt/20180716 Content-Transfer-Encoding: quoted-printable X-Mailing-List: archive/latest/343447 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/20200330185137.wd5nlpazwgvm2y3v@sar0.p1otr.com Approved: robomod@news.nic.it Lines: 27 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Mon, 30 Mar 2020 20:51:37 +0200 X-Original-Message-ID: <20200330185137.wd5nlpazwgvm2y3v@sar0.p1otr.com> X-Original-References: <3fed69b7-6801-a112-8c4b-e23a1b931fda@debian.org> <158557500106.973286.5690503045836220592@hoothoot> <20200330140829.GA673166@espresso.pseudorandom.co.uk> Xref: csiph.com linux.debian.devel:96053 linux.debian.maint.python:12409 > I don't know if I'm missing an argument to dh_python3 so that it knows = the > python version, or even if there's a better workaround. But perhaps pyb= uild better workaround is to force cmake to install into versioned dist-packages (that's what I do in distutils) as I didn't find a reliable way to read Python version/architecture/tag/etc. from .so file > should be doing this automatically between the dh_auto_install calls so= that > this kind of workarounds aren't necessary. it's actually a nice idea - pybuild can check if /usr/lib/python3.X/dist-packages/ is empty and there are .so files in /usr/lib/python3/dist-packages/ and move them temporarily to /usr/lib/python3.X/dist-packages/ (it knows which interpreter is used at this point) and let dh_python3 rename them later > Piotr, is this a bug in pybuild, or am I doing something wrong? well, cmake is not really easy to work with, they provide -DPYTHON_LIBRARY:FILEPATH=E2=80=A6=C2=A0but they don't use it or use comp= letely different name=E2=80=A6=C2=A0it basically is different for each library I= checked (and in different official documentation versions I read, sic!)