all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: Guix-devel <guix-devel@gnu.org>
Subject: Python: inputs vs. propagated inputs
Date: Sun, 18 Sep 2016 20:53:56 +0200	[thread overview]
Message-ID: <67bb3997-bb9a-6699-1dca-d14889e8eefe@crazy-compilers.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2290 bytes --]

Hi,

I still do not get whether python packages required at run-time need to
be inputs or propagated inputs.

The part about inputs, native-inputs and propagated-inputs in section
"package Reference" explicitly states Python as an example where
propagated-inputs are needed. Neither the section about the
python-build-system nor the python packaging guidelines give any other
hints.

In gnu/packages/python.scm there are modules using only inputs (e.g.
python-ccm), some are using propagated-inputs (e.g.
python-scikit-image), some using both (e.g. python-paramiko). I can not
see any clear rule being followed.

Also I see a lot of packages defining python-node, python-mock or
python-pytest as inputs (e.g. python-mathplotlib). But these package are
for tests only and tests AFAIK are never run when cross-compiling. Thus
these packages ASAIK are never needed as inputs, only as native-inputs.

I'd like to understand when to put a package where and have a clear rule
like this:

    For Python modules
    - Every Python-package required at run-time need to go into
    propagated inputs.
    - Python packages required only for building or testing go into
    native-inputs. Examples are setuptools, pytest, mock, and nose. Of
    course if one of these packages is required at run-time, it needs to
    be set in propagated-inputs.
    - "inputs" only contain programs or C-libraries (and such) required
    for building python packages containing c-extensions (or such).
    - If a Python package has optional extra dependencies
    (extras_require), not these are not listed here at all - except if
    there is a test-case in which case they are added to native-inputs.
    - If a packages has complicated optional extra dependencies you may
    want to define another package to ease resolving these dependencies
    for the user. E.g. python-projectaaa-ssh inherits python-projectaaa
    and adds the dependencies required for the "ssh" extra feature.

Please comment on these rules. If we agree on a ruleset, I'll prepare a
path for the documentation.

-- 
Regards
Hartmut Goebel

| Hartmut Goebel          | h.goebel@crazy-compilers.com               |
| www.crazy-compilers.com | compilers which you thought are impossible |


[-- Attachment #2: Type: text/html, Size: 2926 bytes --]

             reply	other threads:[~2016-09-18 18:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-18 18:53 Hartmut Goebel [this message]
2016-09-19  7:45 ` Python: inputs vs. propagated inputs Ricardo Wurmus
2016-10-03 16:13   ` Ludovic Courtès

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=67bb3997-bb9a-6699-1dca-d14889e8eefe@crazy-compilers.com \
    --to=h.goebel@crazy-compilers.com \
    --cc=guix-devel@gnu.org \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.