From: ludo@gnu.org (Ludovic Courtès)
To: Andreas Enge <andreas@enge.fr>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] gnu: Add Scikit-learn.
Date: Thu, 26 Feb 2015 18:11:03 +0100 [thread overview]
Message-ID: <87bnkg61js.fsf@gnu.org> (raw)
In-Reply-To: <20150225225740.GA13495@debian> (Andreas Enge's message of "Wed, 25 Feb 2015 23:57:40 +0100")
Andreas Enge <andreas@enge.fr> skribis:
> Some modules are compatible with only one version of Python, others with both.
> -If the package Foo compiles only with Python 3, we name it
> +If the module Foo compiles only with Python 3, we name it
> @code{python-foo}; if it compiles only with Python 2, we name it
> @code{python2-foo}. If it is compatible with both versions, we create two
> packages with the corresponding names.
>
> -If a project already contains the word @code{python}, we drop this;
> +If a module name already contains the word @code{python}, we drop this;
> for instance, the module python-dateutil is packaged under the names
> @code{python-dateutil} and @code{python2-dateutil}.
I think a Python “module” is a single .py file. In that case “package”
seems more accurate, no?
Ludo’.
next prev parent reply other threads:[~2015-02-26 17:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-23 16:24 [PATCH] gnu: Add Scikit-learn Ricardo Wurmus
2015-02-23 17:17 ` Ricardo Wurmus
2015-02-23 17:36 ` Andreas Enge
2015-02-26 11:28 ` Ricardo Wurmus
2015-02-26 20:44 ` Andreas Enge
2015-02-23 17:52 ` Andreas Enge
2015-02-25 22:52 ` Andreas Enge
2015-02-25 22:57 ` Andreas Enge
2015-02-26 17:11 ` Ludovic Courtès [this message]
2015-02-26 17:59 ` Andreas Enge
2015-02-26 18:20 ` Ludovic Courtès
2015-02-26 18:23 ` Andreas Enge
2015-02-26 20:03 ` Eric Bavier
2015-02-26 20:43 ` Andreas Enge
2015-02-26 21:10 ` Eric Bavier
2015-02-27 9:41 ` Andreas Enge
2015-02-27 22:48 ` Andreas Enge
2015-02-27 23:53 ` Andreas Enge
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bnkg61js.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.