guix-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] gnu: Add python-ply and python2-ply.


From: Leo Famulari
Subject: Re: [PATCH] gnu: Add python-ply and python2-ply.
Date: Mon, 6 Jun 2016 22:26:25 -0400
User-agent: Mutt/1.6.0 (2016-04-01)

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.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]