From: Tanguy Le Carrour <tanguy@bioneland.org>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: "Ludovic Courtès" <ludo@gnu.org>, 42390-done@debbugs.gnu.org
Subject: [bug#42390] [PATCH] gnu: Add python-mamba.
Date: Mon, 27 Jul 2020 10:10:12 +0200 [thread overview]
Message-ID: <20200727081012.yc3u6t3nmm3k3uli@melmoth> (raw)
In-Reply-To: <4266ee5e-b45a-86d6-42db-f8bace0ea298@crazy-compilers.com>
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
next prev parent reply other threads:[~2020-07-27 8:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-16 12:25 [bug#42390] [PATCH] gnu: Add python-mamba Tanguy Le Carrour
2020-07-21 16:41 ` bug#42390: " Ludovic Courtès
2020-07-22 7:36 ` [bug#42390] " Tanguy Le Carrour
2020-07-22 10:38 ` Ludovic Courtès
2020-07-23 19:19 ` Hartmut Goebel
2020-07-24 6:36 ` Tanguy Le Carrour
2020-07-24 13:14 ` Ludovic Courtès
2020-07-27 7:47 ` Hartmut Goebel
2020-07-27 8:10 ` Tanguy Le Carrour [this message]
2020-07-28 21:56 ` Ludovic Courtès
2020-07-29 6:52 ` Tanguy Le Carrour
2020-07-31 6:42 ` Tanguy Le Carrour
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200727081012.yc3u6t3nmm3k3uli@melmoth \
--to=tanguy@bioneland.org \
--cc=42390-done@debbugs.gnu.org \
--cc=h.goebel@crazy-compilers.com \
--cc=ludo@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.