unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Cyril Roelandt <tipecaml@gmail.com>
To: guix-devel@gnu.org
Subject: Re: Naming scheme for Python packages
Date: Wed, 04 Sep 2013 22:52:08 +0200	[thread overview]
Message-ID: <52279D78.7080802@gmail.com> (raw)
In-Reply-To: <87li3c8g56.fsf@gnu.org>

On 09/04/2013 10:51 PM, Ludovic Courtès wrote:
> Andreas Enge <andreas@enge.fr> skribis:
>
>> commit 89114f39e4be7ac655fbdd7f00a5f985c8f4ce6b
>> Author: Andreas Enge <andreas@enge.fr>
>> 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")
>        ...))
>

This is quite Debianish. I like it.


Cyril.

  reply	other threads:[~2013-09-04 21:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1VHJTB-0006ys-7X@vcs.savannah.gnu.org>
2013-09-04 20:51 ` Naming scheme for Python packages Ludovic Courtès
2013-09-04 20:52   ` Cyril Roelandt [this message]
2013-09-04 21:16     ` Andreas Enge
2013-09-04 21:07   ` Cyril Roelandt
2013-09-04 21:36     ` Andreas Enge
2013-09-04 21:08   ` Andreas Enge
2013-09-04 21:32     ` Andreas Enge
2013-09-05 13:00       ` Ludovic Courtès
2013-09-06 21:53         ` Andreas Enge
2013-09-07 12:49           ` Ludovic Courtès
2013-09-07 21:25             ` Andreas Enge
2013-09-08 14:03               ` Ludovic Courtès
2013-09-08 14:51                 ` Andreas Enge
2013-09-08 20:00                   ` Ludovic Courtès

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=52279D78.7080802@gmail.com \
    --to=tipecaml@gmail.com \
    --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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).