[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: Wed, 04 Apr 2018 22:13:26 +0200
User-agent: mu4e 1.0; emacs 25.3.1

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.


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


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

reply via email to

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