From: ludo@gnu.org (Ludovic Courtès)
To: Federico Beffa <beffa@ieee.org>
Cc: 宋文武 <iyzsong@openmailbox.org>, Guix-devel <guix-devel@gnu.org>,
20889@debbugs.gnu.org
Subject: Re: Tkinter moved to separate output
Date: Tue, 01 Dec 2015 23:00:39 +0100 [thread overview]
Message-ID: <87y4dd3k3c.fsf@gnu.org> (raw)
In-Reply-To: <CAKrPhPM0UqgC0x+pOqR7Ta7afGchG6KGaBqfwp+OB2RoaAMQpg@mail.gmail.com> (Federico Beffa's message of "Tue, 1 Dec 2015 21:19:14 +0100")
Federico Beffa <beffa@ieee.org> skribis:
> The attached patch fixes the problem and I can now plot with TkAgg :-)
>
> Thanks for making Tkinter available!
> Fede
>
> From b40cf5522bcc15166ca07dfbae50167203d29e2d Mon Sep 17 00:00:00 2001
> From: Federico Beffa <beffa@fbengineering.ch>
> Date: Tue, 1 Dec 2015 17:20:59 +0100
> Subject: [PATCH 1/2] gnu: python-matplotlib: Add 'TkAgg' backend and update to
> version '1.4.3'.
>
> * gnu/packages/python.scm (python-matplotlib): Do it.
> * gnu/packages/patches/matplotlib-setupext-tk.patch: New file.
Nice!
Please make sure to add the patch to gnu-system.am, but otherwise looks
great!
Thanks for fixing it!
I gather this addresses http://bugs.gnu.org/20888, right?
Ludo’.
next prev parent reply other threads:[~2015-12-01 22:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-01 20:19 Tkinter moved to separate output Federico Beffa
2015-12-01 22:00 ` bug#20889: " Ludovic Courtès
2015-12-01 22:00 ` Ludovic Courtès [this message]
2015-12-02 17:28 ` Federico Beffa
2015-12-02 17:28 ` bug#20889: " Federico Beffa
-- strict thread matches above, loose matches on Subject: below --
2015-11-12 5:50 [PATCH] tk: Hardcode path to TK_LIBRARY 宋文武
2015-11-12 12:58 ` Ludovic Courtès
2015-11-16 8:42 ` bug#20889: Tkinter moved to separate output Ludovic Courtès
2015-11-16 11:44 ` Federico Beffa
2015-11-16 12:57 ` Ludovic Courtès
2015-11-16 13:16 ` Federico Beffa
2015-11-29 22:09 ` Ludovic Courtès
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=87y4dd3k3c.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=20889@debbugs.gnu.org \
--cc=beffa@ieee.org \
--cc=guix-devel@gnu.org \
--cc=iyzsong@openmailbox.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 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.