unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Edouard Klein <edk@beaver-labs.com>
To: 41889@debbugs.gnu.org
Subject: [bug#41889] [PATCH] gnu: jupyter: Fix python-ipython conflict that prevented installation
Date: Tue, 16 Jun 2020 11:21:15 +0200	[thread overview]
Message-ID: <87lfkn9xis.fsf@alice.lan> (raw)
In-Reply-To: <87o8pj9ymu.fsf@alice.lan>

[-- Attachment #1: 2020-06-15T10:51:13+02:00.png --]
[-- Type: image/png, Size: 235609 bytes --]

[-- Attachment #2: 2020-06-16T10:43:36+02:00.png --]
[-- Type: image/png, Size: 228969 bytes --]

[-- Attachment #3: Type: text/plain, Size: 1524 bytes --]

Hi all,

Here is my proposed correction for the breakage I introduced when I
updated python-prompt-toolkit (bugs #41738, #41729 and 41730).

As you can see on the attached images, I disconnected all packages that
depend on ppt2 from the packages that depend on ppt3.
This should fix all reported problems. If it does not, this means that
there is an undeclared dependency, which is a bug. Please do not
hesitate to tell me about any problem you encounter that my be tied to
this change.

jupyter's &co dependency on ppt2 is still a mystery to me. It is computed
by the setuptools when they run but nowhere in the source of the
packages that have an explicit dependency on ppt2 was I able to find any
reference to it.

I have no idea how setuptools comes to the conclusion that it needs
"prompt_toolkit<2.1.0,>=2.0.0". I (grep -r -i)-ed, in the source code of
ipywidgets and could not find anything. This is black magic to me.

I would have loved to bring all those packages to ppt3 and forget about
ppt2 altogether, but because nowhere in the source is the dependency
written, I can't do it. Any help would be appreciated. In the meantime
this fix should do the trick.

I did not repair packages that were broken for reasons unrelated to
ppt, but I'm quite confident that once their brokenness is fixed, ppt3
won't be a problem for them. For example in my dirty work tree I have a
fix for python-rpy2, but it is tied to a pandas upgrade, and too many
packages depend on pandas for me to handle right now.

Cheers,

Edouard.

  reply	other threads:[~2020-06-16  9:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-16  8:57 [bug#41889] [PATCH] gnu: jupyter: Fix python-ipython conflict that prevented installation Edouard Klein
2020-06-16  9:21 ` Edouard Klein [this message]
2020-06-16 16:16 ` [bug#41889] [PATCH] Fix ipython/jupyter Ricardo Wurmus
2020-06-16 17:37 ` bug#41730: [bug#41889] [PATCH] gnu: jupyter: Fix python-ipython conflict that prevented installation Ricardo Wurmus

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=87lfkn9xis.fsf@alice.lan \
    --to=edk@beaver-labs.com \
    --cc=41889@debbugs.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).