From: Ricardo Wurmus <rekado@elephly.net>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: guix-devel@gnu.org
Subject: Re: Python applications that are also libraries
Date: Wed, 04 Apr 2018 22:13:26 +0200 [thread overview]
Message-ID: <87k1tmk9w9.fsf@elephly.net> (raw)
In-Reply-To: <019dbf72-e41b-84ae-405b-cace8053107b@crazy-compilers.com>
Hartmut Goebel <h.goebel@crazy-compilers.com> 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
next prev parent reply other threads:[~2018-04-04 20:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-04 9:36 Python applications that are also libraries Ricardo Wurmus
2018-04-04 11:36 ` Hartmut Goebel
2018-04-04 20:13 ` Ricardo Wurmus [this message]
2018-04-05 7:05 ` Hartmut Goebel
2018-04-06 9:12 ` Chris Marusich
2018-04-06 10:11 ` Hartmut Goebel
2018-04-06 12:12 ` Ricardo Wurmus
2018-04-07 9:27 ` Hartmut Goebel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k1tmk9w9.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@gnu.org \
--cc=h.goebel@crazy-compilers.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).