unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: split up python-pyqt or python-matplotlib?
Date: Mon, 19 Mar 2018 17:55:38 +0100	[thread overview]
Message-ID: <874llcuhrp.fsf@gnu.org> (raw)
In-Reply-To: <87y3iociak.fsf@elephly.net> (Ricardo Wurmus's message of "Mon, 19 Mar 2018 14:21:39 +0100")

Hello,

Ricardo Wurmus <rekado@elephly.net> skribis:

> “python-pyqt” depends on all of Qt.  “python-pyqt” is also an input to
> “python-matplotlib” because that package has a Qt rendering backend.
>
> I wonder if we can make this lighter by default.  The scientific Python
> stack depends on “python-matplotlib”, but it seems like a very expensive
> dependency as it pulls in *all* of Qt *and* Gtk+.
>
> Is it feasible to split up “python-pyqt”?  If not, can we reasonably
> decouple matplotlib from pyqt?

I’m no Pythonista, but would it work to create “python-matplotlib-qt”,
which would contain nothing but the Qt rendering backend?

That way, assuming rendering backends are searched for at run time,
people could choose to install python-matplotlib-qt if they need this
backend.  (Similar to what I did with ‘guile’ vs. ‘guile-readline’.)

HTH,
Ludo’.

  reply	other threads:[~2018-03-19 16:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-19 13:21 split up python-pyqt or python-matplotlib? Ricardo Wurmus
2018-03-19 16:55 ` Ludovic Courtès [this message]
2018-03-19 22:41   ` Hartmut Goebel

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=874llcuhrp.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.net \
    /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).