Hi,
I still do not get whether python packages required at run-time
need to be inputs or propagated inputs.
For Python modulesPlease comment on these rules. If we agree on a ruleset, I'll prepare a path for the documentation.
- 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.
-- Regards Hartmut Goebel | Hartmut Goebel | h.goebel@crazy-compilers.com | | www.crazy-compilers.com | compilers which you thought are impossible |