From: Eric Bavier <ericbavier@gmail.com>
To: Federico Beffa <beffa@ieee.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH 12/13] gnu: Add python2-pygtk.
Date: Sat, 22 Nov 2014 10:18:53 -0600 [thread overview]
Message-ID: <CADwNbn8=fiuA0SCS6m-P4B_kAUg5k0fLzH3dB_sH=h58cu_xeg@mail.gmail.com> (raw)
In-Reply-To: <CAKrPhPMSNE03QRu5qW5wMd8K11t+Usaf-QR=MDN_snvaga_hzg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 837 bytes --]
On Sat, Nov 22, 2014 at 9:40 AM, Federico Beffa <beffa@ieee.org> wrote:
> > Eric Bavier <ericbavier@gmail.com> skribis:
> >
> >> * gnu/packages/gtk.scm (python2-pygtk): New variable.
> >
>
> I notice that most python packages are defined for python 3 and then a
> python2 package is generated with the procedure 'package-with-python2'.
> Is pygtk problematic with python 3?
>
It has been a while since I did the packaging work for this python2-pygtk,
and I seem to recall that there was some sort of difficulty with python3.
> I would be interested in using it
> with a package for matplotlib that I'm preparing.
>
I will take another look at it, being that it would be useful to you.
Thanks for asking,
`~Eric
--
Please avoid sending me Word or PowerPoint attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html
[-- Attachment #2: Type: text/html, Size: 1566 bytes --]
next prev parent reply other threads:[~2014-11-22 16:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-22 15:40 [PATCH 12/13] gnu: Add python2-pygtk Federico Beffa
2014-11-22 16:18 ` Eric Bavier [this message]
2014-11-26 3:46 ` Eric Bavier
2014-11-26 8:30 ` Federico Beffa
2014-11-26 16:50 ` Cyril Roelandt
-- strict thread matches above, loose matches on Subject: below --
2014-11-21 5:40 [PATCH 00/13] Add gourmet (and dependent python packages) Eric Bavier
2014-11-21 5:41 ` [PATCH 12/13] gnu: Add python2-pygtk Eric Bavier
2014-11-21 22:10 ` 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
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='CADwNbn8=fiuA0SCS6m-P4B_kAUg5k0fLzH3dB_sH=h58cu_xeg@mail.gmail.com' \
--to=ericbavier@gmail.com \
--cc=beffa@ieee.org \
--cc=guix-devel@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).