From: Christopher Allan Webber <cwebber@dustycloud.org>
To: "Thompson, David" <dthompson2@worcester.edu>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: gnu: Add python-wtforms.
Date: Fri, 12 Feb 2016 15:42:43 -0800 [thread overview]
Message-ID: <87io1t8pho.fsf@dustycloud.org> (raw)
In-Reply-To: <CAJ=RwfZv+CErcbkcAbWuPa6g9=GW2womkqSZiZXfWx-2g5OSbQ@mail.gmail.com>
Thompson, David writes:
> This looks good, Chris! I can tell by looking at the diff that it's
> based on the wip-mediagoblin. If it cleanly applies on master then I
> say "push"!
>
> - Dave
Ha, yeah. I'm trying to get through as many MediaGoblin deps as I can.
Leo Famulari writes:
> On Fri, Feb 12, 2016 at 11:43:56AM -0800, Christopher Allan Webber wrote:
>> From 8de2a4095987efcf1d9b8f1b5d71ba6fc57e12e8 Mon Sep 17 00:00:00 2001
>> From: Christopher Allan Webber <cwebber@dustycloud.org>
>> Date: Thu, 11 Feb 2016 16:16:45 -0800
>> Subject: [PATCH 2/3] gnu: Add python-wtforms
>>
>> * gnu/packages/python.scm (python-wtforms, python2-wtforms): New variables.
>
> It looks good to me, but I wonder if the python-3 variant really needs
> setuptools? If so, okay. If not, can you use the new python2-variant
> system [0] to provide setuptools for python2-wtforms?
>
> [0] Introduced in 48b311b1b3ba
Okay, I'll give that a try, and will make an adjustment if appropriate,
and regardless, push after figuring that out.
Thanks to both of you!
next prev parent reply other threads:[~2016-02-12 23:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-12 19:43 gnu: Add python-wtforms Christopher Allan Webber
2016-02-12 21:52 ` Thompson, David
2016-02-12 23:42 ` Christopher Allan Webber [this message]
2016-02-12 23:57 ` Leo Famulari
2016-02-13 21:55 ` Christopher Allan Webber
2016-02-13 22:23 ` Leo Famulari
2016-02-13 22:57 ` Christopher Allan Webber
2016-02-13 23:07 ` Christopher Allan Webber
2016-02-12 22:02 ` Leo Famulari
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=87io1t8pho.fsf@dustycloud.org \
--to=cwebber@dustycloud.org \
--cc=dthompson2@worcester.edu \
--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 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.