From: Leo Famulari <leo@famulari.name>
To: Danny Milosavljevic <dannym+a@scratchpost.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add python-ply and python2-ply.
Date: Mon, 6 Jun 2016 22:26:25 -0400 [thread overview]
Message-ID: <20160607022625.GA29348@jasmine> (raw)
In-Reply-To: <20160607010110.52922ed9@scratchpost.org>
On Tue, Jun 07, 2016 at 01:01:10AM +0200, Danny Milosavljevic wrote:
Thanks for the patch!
> * gnu/packages/python.scm (python-ply, python2-ply): New variables.
> + (uri (string-append
> + "https://pypi.python.org/packages/96/e0/"
> + "430fcdb6b3ef1ae534d231397bee7e9304be14a47a267e82ebcb3323d0b5/ply-"
> + version
> + ".tar.gz"))
We should adapt pypi-uri to handle the new scheme, but in the meantime,
can you put the hash on its own line, to reduce noise in the commit log
for future updates? This would be the whole thing:
"96/e0/430fcdb6b3ef1ae534d231397bee7e9304be14a47a267e82ebcb3323d0b5/"
> + (inputs
> + `(("python-setuptools" ,python-setuptools)))
Does it use setuptools at run-time or just at build time? If the former,
then it can be a native-input. Also, if it's only required for the
python-2 version, can you use the python2-variant system as shown in the
package definition of python2-pyicu?
> + (description "ply is an lex/yacc implemented purely in Python. It uses
> +LR parsing and does extensive error checking.")
`guix lint` prefers to begin the description with a capital 'P'.
Also, it's nice to wrap 'lex' and 'yacc' in Texinfo markup like this:
@code{lex}. Then, the word 'lex' will be rendered specially. I'm not
sure if we have a policy on this but I think it's useful when referring
to other packages.
next prev parent reply other threads:[~2016-06-07 2:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-06 23:01 [PATCH] gnu: Add python-ply and python2-ply Danny Milosavljevic
2016-06-07 2:26 ` Leo Famulari [this message]
2016-06-07 6:27 ` [PATCHv2] " Danny Milosavljevic
2016-06-07 17:32 ` 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=20160607022625.GA29348@jasmine \
--to=leo@famulari.name \
--cc=dannym+a@scratchpost.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 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.