[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Naming scheme for Python packages
From: |
Ludovic Courtès |
Subject: |
Naming scheme for Python packages |
Date: |
Wed, 04 Sep 2013 22:51:17 +0200 |
User-agent: |
Gnus/5.130007 (Ma Gnus v0.7) Emacs/24.3 (gnu/linux) |
Andreas Enge <address@hidden> skribis:
> commit 89114f39e4be7ac655fbdd7f00a5f985c8f4ce6b
> Author: Andreas Enge <address@hidden>
> Date: Wed Sep 4 22:12:33 2013 +0200
>
> gnu: python: Implement the python naming scheme for pytz and babel.
>
> * gnu/packages/python.scm (pytz): Rename this ...
> * gnu/packages/python.scm (python-pytz): ... to this
> * gnu/packages/python.scm (python2-pytz): New variable, input python-2.
> * gnu/packages/python.scm (babel): Rename this ...
> * gnu/packages/python.scm (python-babel): ... to this
> * gnu/packages/python.scm (python2-babel): New variable, input python-2.
I think I wasn’t clear when we discussed the policy: I think package
names must be prefixed by “python-”. By “package name” I mean the
‘name’ field of packages, which is what is exposed to the users.
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
(name "python-pytz")
...))
WDYT?
Ludo’.
- Naming scheme for Python packages,
Ludovic Courtès <=