unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] Add optional dependencies to ipython.
Date: Wed, 27 May 2015 17:28:04 +0200	[thread overview]
Message-ID: <87twuyghvf.fsf@gnu.org> (raw)
In-Reply-To: <idjoal6h1ny.fsf@bimsb-sys02.mdc-berlin.net> (Ricardo Wurmus's message of "Wed, 27 May 2015 10:20:33 +0200")

Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de> skribis:

>>> From 9243823abad3943bd3f4ebe4f6d18cc53c2143e0 Mon Sep 17 00:00:00 2001
>>> From: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
>>> Date: Thu, 21 May 2015 15:24:11 +0200
>>> Subject: [PATCH] gnu: python-ipython: Add optional dependencies.
>>>
>>> * gnu/packages/python.scm (python-ipython)[inputs]: Add optional dependencies
>>>   "python-tornado" and "python-pyzmq".
>>
>> LGTM.  One question though: how much does it add to the ipython’s
>> closure size, and is it something that many ipython users would have
>> little use for?
>>
>> IOW, the popularity/extra-space ratio should be greater than one.  :-)

[...]

> I don't know if support for python-tornado and python-pyzmq in
> python-ipython is worth an additional 82 MB.

My guess is that no, it’s not worth it.  So let’s leave it this way,
maybe adding a comment to the future reader who wonders why these two
are missing.

Now, 683 MiB is already a lot, and it would be interesting to analyze
why it’s so big.

Thanks!

Ludo’.

  reply	other threads:[~2015-05-27 15:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-21 13:25 [PATCH] Add optional dependencies to ipython Ricardo Wurmus
2015-05-21 19:58 ` Ludovic Courtès
2015-05-27  8:20   ` Ricardo Wurmus
2015-05-27 15:28     ` Ludovic Courtès [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-07-18  9:25 Federico Beffa

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=87twuyghvf.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=ricardo.wurmus@mdc-berlin.de \
    /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).