unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: Naming scheme for Python packages
Date: Thu, 05 Sep 2013 15:00:27 +0200	[thread overview]
Message-ID: <87hadz5spg.fsf@gnu.org> (raw)
In-Reply-To: <20130904213224.GA8767@debian> (Andreas Enge's message of "Wed, 4 Sep 2013 23:32:24 +0200")

Andreas Enge <andreas@enge.fr> 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’.

  reply	other threads:[~2013-09-05 13:05 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
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 [this message]
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=87hadz5spg.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=andreas@enge.fr \
    --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).