all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Marius Bakke <mbakke@fastmail.com>
To: Thomas Danckaert <post@thomasdanckaert.be>, guix-devel@gnu.org
Subject: Re: [PATCH] gnu: python-matplotlib: Don't propagate	python-numpy-bootstrap.
Date: Fri, 27 Jan 2017 20:57:12 +0100	[thread overview]
Message-ID: <87lgtw1dk7.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <20170127.160509.2073167591783697985.post@thomasdanckaert.be>

[-- Attachment #1: Type: text/plain, Size: 937 bytes --]

Hi Thomas,

Thomas Danckaert <post@thomasdanckaert.be> writes:

> Hi,
>
> when a profile contains both python-numpy and python-matplotlib
> (either installed directly or by propagation, e.g. when from
> python-ipython), a lot of warnings about conflicts between
> python-numpy and python-nympy-bootstrap appear, because matplotlib
> propagates its python-numpy-bootstrap dependency.

Ouch.

> This patch works around it by creating an intermediate
> python-matplotlib-bootstrap package as well, which is then used as a
> native input to generate the documentation of python-numpy.
> python-numpy is then used as a propagated input of python-matplotlib,
> so python-numpy-bootstrap doesn't appear in user's profiles anymore.
>
> What do you think?

This sounds sensible. Does numpy not require any matplotlib functions at
runtime? If so, this patch LGTM. The new matplotlib-bootstrap variables
should have an explaining comment though :)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  reply	other threads:[~2017-01-27 19:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-27 15:05 [PATCH] gnu: python-matplotlib: Don't propagate python-numpy-bootstrap Thomas Danckaert
2017-01-27 19:57 ` Marius Bakke [this message]
2017-01-30 10:26   ` Thomas Danckaert

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=87lgtw1dk7.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me \
    --to=mbakke@fastmail.com \
    --cc=guix-devel@gnu.org \
    --cc=post@thomasdanckaert.be \
    /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.