On 20-12-2024 08:14, Tom wrote:
>
>
>> On 19 Dec 2024, at 05:56, Nick via Dng <dng@???> wrote:
>>
>> There is a Debian oletools
>> https://packages.debian.org/search?searchon=names&keywords=python3-olefile.
>>
>
> It looks like that is just a python module and not the end-user tools
> that oletools provides.
>
>> And if you definitive wants to use pip you use:
>>
>> pip3 install oletools --break-system-packages
>
> Please don’t use that option or recommend it to others.
>
> https://discuss.python.org/t/the-most-popular-advice-on-the-internet-for-error-externally-managed-environment-is-to-force-packages-to-be-system-installed/56900
>
> PEP-668 will tell you all the details if you want to know more.
>
> https://peps.python.org/pep-0668/
>
> The solution here is to install pipx and use that to install oletools.
>
> https://pipx.pypa.io/stable/
>
> apt-get install pipx
> pipx install oletools
>
> This is also recommended as one of the install methods on the oletools
> wiki.
>
> https://github.com/decalage2/oletools/wiki/Install
>
> Tom

For clarity I think that the use of pipx is indeed the better choice
especially when you build your own docker image. If not possible and you
desperate need a python module not available in your distro of choice
and not compatible with pipx than you still have this possibility as a
last resort. And within a docker container the potential problems with
conflicting OS packaged modules are limited to that container. Outside a
container I personally still like to use virtenv.