Re: How to handle a testing only python package dependency

Miklos Vajna <vmiklos -AT- collabora.com>

Fri, 16 Aug 2019 09:31:39 +0200

Hi Markus, On Thu, Aug 15, 2019 at 03:24:19AM +0800, Markus Mohrhard <markus.mohrhard@googlemail.com> wrote:

What is our policy about python packages that are actually not needed for
an installed LibreOffice?

I think most build-time dependencies are simply mandated by configure, and then either provided manually or via lode (think of doxygen, gperf, etc.)

My current solution would be to add an explicit ImportError check in the
script and tell the person calling the script to install the package. As
this is mostly something for a few selected QA team members this seems like
an acceptable solution.

Any other solutions/opinions?

Sounds good to me. It's similar to e.g. bin/find-unneeded-includes, where the few ones who actually use it will take care of installing the underlying dependency and others are not forced to install it. Regards, Miklos

Attachment: signature.asc
Description: Digital signature

Context

How to handle a testing only python package dependency · Markus Mohrhard

Re: How to handle a testing only python package dependency · Miklos Vajna

Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.