[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug#42390] [PATCH] gnu: Add python-mamba.
From: |
Tanguy Le Carrour |
Subject: |
[bug#42390] [PATCH] gnu: Add python-mamba. |
Date: |
Mon, 27 Jul 2020 10:10:12 +0200 |
Le 07/27, Hartmut Goebel a écrit :
> Am 24.07.20 um 15:14 schrieb Ludovic Courtès:
> > To me, we should keep python-coverage in the list only if we know it
> > should be a native input 90% of the time.
>
> > 90%
>
> Rational: Checking code-coverage is a typical part of testing, thus like
> other testing-tools, coverage is required native. The only case, this
> module is *not* a native input are test-suites/test-runner like
> python-mamba.
+1!
The question is now: is it possible to make the warning go away by
marking it as being an "exception" in the package definition?
Are comments "part of the code" and be used for that? Can we use a
different package name (`python-coverage-propagated`) that would not
be in the list?
--
Tanguy
- [bug#42390] [PATCH] gnu: Add python-mamba., Tanguy Le Carrour, 2020/07/16
- bug#42390: [PATCH] gnu: Add python-mamba., Ludovic Courtès, 2020/07/21
- [bug#42390] [PATCH] gnu: Add python-mamba., Tanguy Le Carrour, 2020/07/22
- [bug#42390] [PATCH] gnu: Add python-mamba., Ludovic Courtès, 2020/07/22
- [bug#42390] [PATCH] gnu: Add python-mamba., Hartmut Goebel, 2020/07/23
- [bug#42390] [PATCH] gnu: Add python-mamba., Tanguy Le Carrour, 2020/07/24
- [bug#42390] [PATCH] gnu: Add python-mamba., Ludovic Courtès, 2020/07/24
- [bug#42390] [PATCH] gnu: Add python-mamba., Hartmut Goebel, 2020/07/27
- [bug#42390] [PATCH] gnu: Add python-mamba.,
Tanguy Le Carrour <=
- [bug#42390] [PATCH] gnu: Add python-mamba., Ludovic Courtès, 2020/07/28
- [bug#42390] [PATCH] gnu: Add python-mamba., Tanguy Le Carrour, 2020/07/29
[bug#42390] [PATCH] gnu: Add python-mamba., Tanguy Le Carrour, 2020/07/31