[Top][All Lists]

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

Re: Python applications that are also libraries

From: Ricardo Wurmus
Subject: Re: Python applications that are also libraries
Date: Fri, 06 Apr 2018 14:12:06 +0200
User-agent: mu4e 1.0; emacs 25.3.1

Chris Marusich <address@hidden> writes:

> Ricardo Wurmus <address@hidden> writes:
>> we have a bunch of packages that are used both as applications and as
>> Python libraries.  An example is “deeptools”.
> I took a brief peek at deeptools.  It looks like there are programs in
> bin, and libraries in lib.  Why can't we just split them into two
> outputs?  For example, put the libraries into the default "out" output
> and the programs into the "bin" output.

The programs in “bin” use the libraries in “lib”.  The binaries aren’t
big, so separating them from the lib output provides hardly any benefit.

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.


GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC

reply via email to

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