[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Naming scheme for Python packages
From: |
Ludovic Courtès |
Subject: |
Re: Naming scheme for Python packages |
Date: |
Thu, 05 Sep 2013 15:00:27 +0200 |
User-agent: |
Gnus/5.130007 (Ma Gnus v0.7) Emacs/24.3 (gnu/linux) |
Andreas Enge <address@hidden> skribis:
> Apparently, I am getting tired. Especially the variable names must be
> distinct: There is python-pytz (as a module for python=python-3) and
> python2-pytz (as a module for python-2) inside the same scheme module.
Oh, good point. Well, OK then.
(In guile.scm we used a different convention: ‘guile-reader/guile-1.8’
vs. ‘guile-reader/guile-2.0’, where ‘/’ reads as ‘over’; the ‘name’
field follows a weird convention.)
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 write:
(define python2-pytz
(package-with-explicit-python python-pytz python-2))
Ludo’.
- Naming scheme for Python packages, Ludovic Courtès, 2013/09/04
- Re: Naming scheme for Python packages, Cyril Roelandt, 2013/09/04
- Re: Naming scheme for Python packages, Cyril Roelandt, 2013/09/04
- Re: Naming scheme for Python packages, Andreas Enge, 2013/09/04
- Re: Naming scheme for Python packages, Andreas Enge, 2013/09/04
- Re: Naming scheme for Python packages,
Ludovic Courtès <=
- Re: Naming scheme for Python packages, Andreas Enge, 2013/09/06
- Re: Naming scheme for Python packages, Ludovic Courtès, 2013/09/07
- Re: Naming scheme for Python packages, Andreas Enge, 2013/09/07
- Re: Naming scheme for Python packages, Ludovic Courtès, 2013/09/08
- Re: Naming scheme for Python packages, Andreas Enge, 2013/09/08
- Re: Naming scheme for Python packages, Ludovic Courtès, 2013/09/08