[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH 01/10] gnu: Add python-pytest-cov.
|
From: |
Ricardo Wurmus |
|
Subject: |
Re: [PATCH 01/10] gnu: Add python-pytest-cov. |
|
Date: |
Thu, 3 Dec 2015 23:25:26 +0100 |
|
User-agent: |
mu4e 0.9.13; emacs 24.5.1 |
Efraim Flashner <address@hidden> writes:
> + (build-system python-build-system)
> + (inputs
> + `(("python-coverage" ,python-coverage)
> + ("python-pytest" ,python-pytest)))
If these Python modules need to be available at runtime they really
should be propagated-inputs. If they are needed at test time only, they
should be native-inputs. For Python packages there is rarely a good
reason to use inputs unless they are library bindings.
I think many of our Python packages actually need to declare many more
inputs as propagated inputs.
> + (native-inputs
> + `(("python-setuptools" ,python-setuptools)))
~~ Ricardo
[PATCH 01/10] gnu: Add python-pytest-cov., Efraim Flashner, 2015/12/03
- Re: [PATCH 01/10] gnu: Add python-pytest-cov.,
Ricardo Wurmus <=
- Re: [PATCH 01/10] gnu: Add python-pytest-cov., Efraim Flashner, 2015/12/07
- Re: [PATCH 01/10] gnu: Add python-pytest-cov., Ricardo Wurmus, 2015/12/11
- Re: [PATCH 01/10] gnu: Add python-pytest-cov., Efraim Flashner, 2015/12/19
- Re: [PATCH 01/10] gnu: Add python-pytest-cov., Ricardo Wurmus, 2015/12/20
- Re: [PATCH 01/10] gnu: Add python-pytest-cov., Efraim Flashner, 2015/12/27
- Re: [PATCH 01/10] gnu: Add python-pytest-cov., Ricardo Wurmus, 2015/12/30
- Re: [PATCH 01/10] gnu: Add python-pytest-cov., Efraim Flashner, 2015/12/30
- Re: [PATCH 01/10] gnu: Add python-pytest-cov., Ricardo Wurmus, 2015/12/30
- Re: [PATCH 01/10] gnu: Add python-pytest-cov., Mathieu Lirzin, 2015/12/31
- Re: [PATCH 01/10] gnu: Add python-pytest-cov., Ricardo Wurmus, 2015/12/31