From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add python-gunicorn and python2-gunicorn.
Date: Tue, 13 Sep 2016 21:22:03 +0200 [thread overview]
Message-ID: <57D851DB.2000306@crazy-compilers.com> (raw)
In-Reply-To: <20160913155133.GC13516@jasmine>
Am 13.09.2016 um 17:51 schrieb Leo Famulari:
> Thanks for this! Regarding the naming question, I think it's fine to
> call it 'gunicorn'. Prefixing with 'python-' is more appropriate for
> libraries and other "helper" packages, whereas user facing or
> standalone applications can use the plain upstream name, in my opinion.
Fine. I'll update (which may take until Thursday) the patch.
>> + ;("python-pytest-cov" ,python-pytest-cov) ; optional
> I think we should either use pytest-cov or remove this commented line.
> What do you think?
I added this line for documentation reasons. But I agree, it's better to
remove this line and add a real comment.
>> +(define-public python2-gunicorn
>> + (let ((base (package-with-python2
>> + (strip-python2-variant python-gunicorn))))
>> + ; Note: byte-compiling gunicorn/workers/_gaiohttp.py with Python 2
>> + ; fails, but this module will be available for Python 3 only
>> + ; anyway.
> Can you elaborate on this? Does python2-gunicorn still work? If so,
> okay.
Yes. I'll update this comment to make it more clear, too.
--
Regards
Hartmut Goebel
| Hartmut Goebel | h.goebel@crazy-compilers.com |
| www.crazy-compilers.com | compilers which you thought are impossible |
prev parent reply other threads:[~2016-09-13 19:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-11 20:50 [PATCH] gnu: Add python-gunicorn and python2-gunicorn Hartmut Goebel
2016-09-12 7:48 ` Hartmut Goebel
2016-09-13 15:51 ` Leo Famulari
2016-09-13 19:22 ` Hartmut Goebel [this message]
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=57D851DB.2000306@crazy-compilers.com \
--to=h.goebel@crazy-compilers.com \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/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).