[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Python applications that are also libraries

From: Hartmut Goebel
Subject: Re: Python applications that are also libraries
Date: Sat, 7 Apr 2018 11:27:37 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0

Am 06.04.2018 um 14:12 schrieb Ricardo Wurmus:
> The point here is that in the library case inputs must be propagated,
> whereas in the case where only the executables are used the inputs don’t
> have to be propagated.
> Separating them in two outputs doesn’t address this problem as far as I
> can see.
Using the venv-based wrapper I describe in
could avoid propagating for the scripts - but not for the libs.

IMHO it does not make much sense having "script" packages without
propagation, as we still need "libs" packages with propagation. Even if
"deeptools:script" would not propagate its inputs, "somepackage:lib"
(required by "deeptools:script") would still need to propagate its
inputs. Thus nothing gained.

Hartmut Goebel

| Hartmut Goebel          | address@hidden               |
| | compilers which you thought are impossible |

reply via email to

[Prev in Thread] Current Thread [Next in Thread]