From: "Ludovic Courtès" <ludo@gnu.org>
To: Tanguy Le Carrour <tanguy@bioneland.org>
Cc: Hartmut Goebel <h.goebel@crazy-compilers.com>,
42390-done@debbugs.gnu.org
Subject: [bug#42390] [PATCH] gnu: Add python-mamba.
Date: Wed, 22 Jul 2020 12:38:05 +0200 [thread overview]
Message-ID: <87v9ifj0mq.fsf@gnu.org> (raw)
In-Reply-To: <20200722073655.qhwhps7dntfipml3@melmoth> (Tanguy Le Carrour's message of "Wed, 22 Jul 2020 09:36:55 +0200")
Howdy,
(+Cc: Hartmut.)
Tanguy Le Carrour <tanguy@bioneland.org> skribis:
> Le 07/21, Ludovic Courtès a écrit :
>> Tanguy Le Carrour <tanguy@bioneland.org> skribis:
>> > * gnu/packages/python-xyz.scm (python-mamba): New variable.
>> […]
>>
>> There’s a lint warning though I don’t know if it’s applicable:
>>
>> --8<---------------cut here---------------start------------->8---
>> gnu/packages/python-xyz.scm:14542:2: python-mamba@0.11.0: 'python-coverage' should probably be a native input
>> --8<---------------cut here---------------end--------------->8---
>>
>> If ‘python-coverage’ is only used at build time, then it should
>> definitely be a native input.
>>
>> WDYT?
>
> I saw the warning (should I have mentioned it in the bug report?),
> but `python-coverage` is definitively a run time dependency.
> If I remove it, I get:
>
> ```
> pkg_resources.DistributionNotFound: The 'coverage' distribution was not found and is required by mamba
> ```
Ah, I see.
> Is there a way to know why the linter is reporting it?!
I don’t know, it comes from commit
e442246a2f5f73b2484adb340b53d3a0018636b1 by Hartmut (Cc’d.)
Hartmut, it looks like there are cases like this where python-coverage
is used as a library and thus should not be in ‘native-inputs’. Should
we remove it from the list?
Thanks,
Ludo’.
next prev parent reply other threads:[~2020-07-22 10:39 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 [this message]
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
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v9ifj0mq.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=42390-done@debbugs.gnu.org \
--cc=h.goebel@crazy-compilers.com \
--cc=tanguy@bioneland.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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).