Re: Python applications that are also libraries

[Ricardo Wurmus]

Hartmut Goebel <address@hidden> writes:

> Am 04.04.2018 um 11:36 schrieb Ricardo Wurmus:
>> I wonder how to deal with this.  Should we assume that these packages
>> are used as libraries and default to propagating all Python inputs?  Or
>> should we have package variants (or outputs?) that propagate inputs as a
>> side-effect?
>
> If this is a "pure" application, I'd install it with*out* propagated
> inputs. This might not be easy to determine, though.

It is both.  It is often used just as an application, but the procedures
that make up the application are just as often used in an interactive
Python session or as a library.

> https://lists.gnu.org/archive/html/guix-devel/2018-02/msg00456.html

This is about wrapping (or not) using virtual envs.  I don’t really see
how this relates to this problem, but maybe I’m missing something
obvious.

--
Ricardo

GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
https://elephly.net