Re: Question regarding binaries in /usr/lib/python3/dist-packages/

Andrey Rakhmatullin <[email protected]> Thu, 23 Apr 2026 23:53:06 +0500

Newsgroups	gmane.linux.debian.devel.python
Message-ID	<[email protected]>

On Thu, Apr 23, 2026 at 11:09:57AM -0700, Soren Stoutner wrote:
>X: python3-pyinstaller: executable-in-usr-lib [usr/lib/python3/dist-packages/
>PyInstaller/bootloader/Linux-64bit-intel/run]
>X: python3-pyinstaller: executable-in-usr-lib [usr/lib/python3/dist-packages/
>PyInstaller/bootloader/Linux-64bit-intel/run_d]

>I do not know how easy it would be to relocate these files.  Before reaching
>out to the Pyinstaller upstream to see of what it would take to relocate these
>files, I wanted to ask the Debian Python Team how this is generally handled
>with Python packages.  

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 
executable helpers suitable for libexec are rare in general and even more 
rare in libraries, they must be very rare in Python library packages so I 
wouldn't be surprised if this situation have never occured in Debian 
packages at all.

On the other hand, shipping data of various kinds in dist-packages/ is 
relatively popular and usually tolerated. This seems to be similar to it, 
and to be honest I would make sure these executables are meant to be 
executed at all, as opposed to being included into the pyinstaller output 
(see "bootloader"), before e.g. contacting the upstream (or the DPT, but 
that's too late).

-- 
WBR, wRAR

signature.asc (application/pgp-signature, 894 B)