From: Federico Beffa <beffa@ieee.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] gnu: Add matplotlib.
Date: Sun, 30 Nov 2014 17:01:02 +0100 [thread overview]
Message-ID: <CAKrPhPNt0QS7rnQs=ExHJoqa=V+Ko9HKpFMYM3nPXDZnBHuXMQ@mail.gmail.com> (raw)
In-Reply-To: <877fydvhs8.fsf@gnu.org>
On Sat, Nov 29, 2014 at 10:05 PM, Ludovic Courtès <ludo@gnu.org> wrote:
> What happens is that ‘package-with-python2’ automatically generates
> python2 variants of the dependencies of the package you give it. So
> (package-with-python2 python-matplotlib) generates a package with an
> input that is exactly (package-with-python2 python-numpydoc), hence with
> #:tests? #t.
Oh, I see. Wouldn't it be better if, for each input,
'pyckage-with-python2' would check if in (gnu packages python) a
variable with prefix 'python2-' is defined and, in case it is, use
that variable instead of constructing new package?
>
> The fix is to explicitly use the right python2-numpydoc, along the lines
> of:
>
> (define-public python2-matplotlib
> (let ((matplotlib (package-with-python2 python-matplotlib)))
> (package (inherit matplotlib)
> ;; Make sure we use exactly PYTHON2-NUMPYDOC, which is
> ;; customized for Python 2.
> (inputs `(("numpydoc" ,python2-numpydoc)
> ,@(alist-delete "numpydoc" (package-inputs matplotlib)))))))
>
>
>> + ;; FIX-ME: Add backends when available.
>
> Please write “FIXME” for easier grepping and highlighting.
>
> Otherwise the patch looks good to me, thanks for working on it!
I've corrected these two items and pushed the patch.
Thanks for the clarification!
Fede
next prev parent reply other threads:[~2014-11-30 16:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-27 19:32 [PATCH] gnu: Add matplotlib Federico Beffa
2014-11-29 21:05 ` Ludovic Courtès
2014-11-30 16:01 ` Federico Beffa [this message]
2014-11-30 17:00 ` Ludovic Courtès
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='CAKrPhPNt0QS7rnQs=ExHJoqa=V+Ko9HKpFMYM3nPXDZnBHuXMQ@mail.gmail.com' \
--to=beffa@ieee.org \
--cc=guix-devel@gnu.org \
--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 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).