From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] python3-ipython: fix broken matplotlib_inline import
Date: Sat, 01 May 2021 22:29:04 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30616@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 679 bytes --]
There is a new pull request by ahesford against master on the void-packages repository
https://github.com/ahesford/void-packages ipython
https://github.com/void-linux/void-packages/pull/30616
python3-ipython: fix broken matplotlib_inline import
Looks like the upstream restructuring introduced a bug. Awaiting either upstream acknowledgment or downstream confirmation that this fix is sufficient.
Issue report: https://www.reddit.com/r/voidlinux/comments/n2nxyd/matplotlib_inline_broken_after_most_recent_update/
Proposed upstream fix: https://github.com/ipython/ipython/pull/12940
A patch file from https://github.com/void-linux/void-packages/pull/30616.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-ipython-30616.patch --]
[-- Type: text/x-diff, Size: 1677 bytes --]
From a4b475435e2d3e825ff8116e3c2b12d1dfa44a42 Mon Sep 17 00:00:00 2001
From: "Andrew J. Hesford" <ajh@sideband.org>
Date: Sat, 1 May 2021 16:23:34 -0400
Subject: [PATCH] python3-ipython: fix broken matplotlib_inline import
---
srcpkgs/python3-ipython/patches/mpl_inline_fix.patch | 12 ++++++++++++
srcpkgs/python3-ipython/template | 2 +-
2 files changed, 13 insertions(+), 1 deletion(-)
create mode 100644 srcpkgs/python3-ipython/patches/mpl_inline_fix.patch
diff --git a/srcpkgs/python3-ipython/patches/mpl_inline_fix.patch b/srcpkgs/python3-ipython/patches/mpl_inline_fix.patch
new file mode 100644
index 000000000000..4526ce4af0e7
--- /dev/null
+++ b/srcpkgs/python3-ipython/patches/mpl_inline_fix.patch
@@ -0,0 +1,12 @@
+diff --git IPython/core/pylabtools.py IPython/core/pylabtools.py
+index c71b0cdb6..bb815956e 100644
+--- IPython/core/pylabtools.py
++++ IPython/core/pylabtools.py
+@@ -383,6 +383,6 @@ def configure_inline_support(shell, backend):
+ stacklevel=2,
+ )
+
+- from matplotlib_inline.backend_inline import configure_inline_support_orig
++ from matplotlib_inline.backend_inline import configure_inline_support as configure_inline_support_orig
+
+ configure_inline_support_orig(shell, backend)
diff --git a/srcpkgs/python3-ipython/template b/srcpkgs/python3-ipython/template
index bf1b012ed3a3..671614a92a1d 100644
--- a/srcpkgs/python3-ipython/template
+++ b/srcpkgs/python3-ipython/template
@@ -1,7 +1,7 @@
# Template file for 'python3-ipython'
pkgname=python3-ipython
version=7.23.0
-revision=1
+revision=2
wrksrc="ipython-${version}"
build_style=python3-module
hostmakedepends="python3-setuptools"
next reply other threads:[~2021-05-01 20:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-01 20:29 ahesford [this message]
2021-05-02 0:09 ` ahesford
2021-05-02 0:09 ` [PR PATCH] [Merged]: " ahesford
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30616@inbox.vuxu.org \
--to=ahesford@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).