Re: Naming scheme for Python packages

2013-09-08 Thread Ludovic Courtès
Andreas Enge andr...@enge.fr skribis: On Sun, Sep 08, 2013 at 04:03:23PM +0200, Ludovic Courtès wrote: Andreas Enge andr...@enge.fr skribis: separate ‘package-with-name-prefix’ procedure, such that we would do: (define package-with-python-2 (compose (cut package-with-name-prefix

Re: Naming scheme for Python packages

2013-09-06 Thread Andreas Enge
On Thu, Sep 05, 2013 at 03:00:27PM +0200, Ludovic Courtès wrote: BTW, I haven’t check whether this is the case already, but we need something like (define (package-with-explicit-python p python) ;; Return a version of P built for PYTHON. (package (inherit p) ...)) so we can just

Re: Naming scheme for Python packages

2013-09-04 Thread Andreas Enge
On Wed, Sep 04, 2013 at 10:52:08PM +0200, Cyril Roelandt wrote: (define pytz (package (name python-pytz) ...)) This is quite Debianish. I like it. But the alternative (as I suggested in the packaging guidelines) is as debianish: (define python-pytz (package

Re: Naming scheme for Python packages

2013-09-04 Thread Cyril Roelandt
On 09/04/2013 10:51 PM, Ludovic Courtès wrote: Thus I would do: (define pytz (package (name python-pytz) ...)) And what should we call python2-pytz ? Cyril.

Re: Naming scheme for Python packages

2013-09-04 Thread Andreas Enge
On Wed, Sep 04, 2013 at 10:51:17PM +0200, Ludovic Courtès wrote: However, I don’t think that scheme should be followed for variable names: it’s tedious to type, and Guile offers mechanisms to select/rename bindings imported from other bindings. Thus I would do: (define pytz (package