[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Python: inputs vs. propagated inputs
From: |
Ricardo Wurmus |
Subject: |
Re: Python: inputs vs. propagated inputs |
Date: |
Mon, 19 Sep 2016 09:45:14 +0200 |
User-agent: |
mu4e 0.9.16; emacs 25.1.1 |
Hartmut Goebel <address@hidden> writes:
> 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.
I’d say “python-ccm” is wrong (not only in using “inputs” but also in
its description).
The exception are Python *applications*. Those usually have a wrapper
to set the PYTHONPATH appropriately. For Python modules we need
propagated-inputs for everything that must be available at runtime.
~~ Ricardo