Path: csiph.com!pasdenom.info!weretis.net!feeder8.news.weretis.net!srl.newsdeef.eu!news.corradoroberto.it!bofh.it!news.nic.it!robomod From: Andrey Rakhmatullin Newsgroups: linux.debian.maint.python Subject: Re: Question regarding binaries in /usr/lib/python3/dist-packages/ Date: Thu, 23 Apr 2026 21:00:01 +0200 Message-ID: References: X-Original-To: debian-python@lists.debian.org X-Mailbox-Line: From debian-python-request@lists.debian.org Thu Apr 23 18:53:25 2026 Old-Return-Path: X-Amavis-Spam-Status: No, score=-12 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, LDO_WHITELIST=-5, PGPSIGNATURE=-5] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate:hard: -3.5 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="ZSuXURXoSP4oNhI/" Content-Disposition: inline X-Mailing-List: archive/latest/23749 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/aepqkv4xo0WpXRwd@belkar.wrar.name Approved: robomod@news.nic.it Lines: 68 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Thu, 23 Apr 2026 23:53:06 +0500 X-Original-Message-ID: X-Original-References: <6743094.KJgs85P2H9@soren-desktop> Xref: csiph.com linux.debian.maint.python:17472 --ZSuXURXoSP4oNhI/ Content-Type: text/plain; charset=utf-8; format=flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Apr 23, 2026 at 11:09:57AM -0700, Soren Stoutner wrote: >X: python3-pyinstaller: executable-in-usr-lib [usr/lib/python3/dist-packag= es/ >PyInstaller/bootloader/Linux-64bit-intel/run] >X: python3-pyinstaller: executable-in-usr-lib [usr/lib/python3/dist-packag= es/ >PyInstaller/bootloader/Linux-64bit-intel/run_d] >I do not know how easy it would be to relocate these files. Before reachi= ng >out to the Pyinstaller upstream to see of what it would take to relocate t= hese >files, I wanted to ask the Debian Python Team how this is generally handled >with Python packages. =20 I don't think there is any need to "generally handle this", to be honest. > Are executables typically relocated to /usr/libexec/? Executables are typically generated in /usr/bin directly. Just as=20 executable helpers suitable for libexec are rare in general and even more= =20 rare in libraries, they must be very rare in Python library packages so I= =20 wouldn't be surprised if this situation have never occured in Debian=20 packages at all. On the other hand, shipping data of various kinds in dist-packages/ is=20 relatively popular and usually tolerated. This seems to be similar to it,= =20 and to be honest I would make sure these executables are meant to be=20 executed at all, as opposed to being included into the pyinstaller output= =20 (see "bootloader"), before e.g. contacting the upstream (or the DPT, but=20 that's too late). --=20 WBR, wRAR --ZSuXURXoSP4oNhI/ Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQJhBAABCgBLFiEEtf6ieDcfC1EgtGkao+OWn23e7IYFAmnqao0tFIAAAAAAFQAP cGthLWFkZHJlc3NAZ251cGcub3Jnd3JhckBkZWJpYW4ub3JnAAoJEKPjlp9t3uyG Gi0QAMm9zAwyl9MlzQN9WtdMOVg3k2duwnG0pDbb9Hyz4gms5LDx9mpD9jbn3yj3 xknxIkGB2sfZQCf4f+qWmfr8BT9hitUT8bAjRjBjxV4HjR+6d4n+y9f/k0swLYlm MACDa6zhCW1rrutgJFT4vKWEUeezRdW0HxCUMQ7Zt8liD6p6gAF3pddIt7hgXpGj QsZ6NgpaEbOnRg22Exa0XHZYDxA+ON4EspKVC3SMrhTo0xPXWwwccBfxO7TvtklC UDQ7H4jljr7D0yf3sImL/YtOvVo0UUxjUcXD90vLl2yzrzZkMUmJC3ra5beTRXTb 2JjDqo9P/3TeNIhgHu5bI1ErF3JoxFEVtWn6UD6PKFCZd0NEs3NZrXDuWvBYCMkE 1Pmpb1Iu7UbxUdm1AZ3NLCzRkppFCxsRWxlx7toFApRfIU9DLqZpYGPiuNrqw2BW Z9qZecgXsRSJ4MkCCWzeKa+h+TuEpEvauUpdko+Oc53INPvzqGHlCfNPl+te7zvh udCzjPFBgnUCKCbIc1zdtcQ+k6f0/AnoWoy2I14JdLNqZfPN1+2Va026m0VdukDp XI7aCnxB4/4EfRcqN55qIu5OcBCqi8u/qp/AI5HwTDIFf8qmt2XyIZUNBTP3peiS SQL657MVxuuyh44yInRoFtQgDVOehqdysIYGogjnbMJJQR14 =MaN3 -----END PGP SIGNATURE----- --ZSuXURXoSP4oNhI/--