[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Python: inputs vs. propagated inputs
From: |
Ludovic Courtès |
Subject: |
Re: Python: inputs vs. propagated inputs |
Date: |
Mon, 03 Oct 2016 18:13:45 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux) |
Hi,
Ricardo Wurmus <address@hidden> skribis:
> 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.
I concur.
Hartmut: if you have ideas on how to clarify this in the manual, that
would be welcome! Probably under “Python Modules”?
Thanks,
Ludo’.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Re: Python: inputs vs. propagated inputs,
Ludovic Courtès <=