From: Efraim Flashner <efraim@flashner.co.il>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: guix-devel@gnu.org, pjotr2019@thebird.nl
Subject: Re: Python package naming: Dots vs hyphens
Date: Wed, 6 Nov 2019 09:19:17 +0200 [thread overview]
Message-ID: <20191106071917.GJ14453@E5400> (raw)
In-Reply-To: <20191106064955.rks6qsypuym6v6pt@pelzflorian.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1666 bytes --]
On Wed, Nov 06, 2019 at 07:49:56AM +0100, pelzflorian (Florian Pelz) wrote:
> Shall I rename python-zope-* to python-zope.*?
>
For new packages I would use whatever upstream uses in regard to '-' vs
'.'. For existing ones, how many are there? It might be best to just
leave them as-is rather than go through the dance of deprecating the old
packages.
> I am in the process of packaging mailman 3 which according to the pypi
> importer needs packages like
>
> python-flufl.bounce
> python-flufl.i18n
> python-flufl.lock
> python-lazr.config
> python-lazr.delegates
> python-zope.component
> python-zope.configuration
> python-zope.configuration
> python-zope.event
> python-zope.interface
>
I've actually last week started working on that. I've only done the
python part, haven't searched for any javascript or font-awesome which
I'm pretty sure I saw. I've also started working on a service for it
which I haven't committed yet, but it looks like it's going to be
complex.
https://gitlab.com/genenetwork/guix-bioinformatics/blob/master/gn/packages/mailman.scm
>
> However the zope ones have already been added since 2fc5f186801, but
> with a hyphen instead of a dot. Which one is correct? Shall I rename
> python-zope-* to python-zope.*? Or shall I correct the pypi importer?
> Ignore it?
>
'guix package -A python-zope' lists them all as having a dash, I'd just
go ahead and make them all dashes.
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-11-06 7:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-06 6:49 Python package naming: Dots vs hyphens pelzflorian (Florian Pelz)
2019-11-06 7:19 ` Efraim Flashner [this message]
2019-11-06 13:13 ` pelzflorian (Florian Pelz)
2019-11-07 7:34 ` Efraim Flashner
2019-11-06 13:18 ` Mailman packaging (was: Re: Python package naming: Dots vs hyphens) pelzflorian (Florian Pelz)
2019-11-13 22:16 ` pelzflorian (Florian Pelz)
2019-11-18 10:13 ` Efraim Flashner
2019-11-18 13:14 ` pelzflorian (Florian Pelz)
2019-11-20 16:36 ` Pjotr Prins
2021-09-29 16:34 ` Christine Lemmer-Webber
2021-09-30 7:54 ` pelzflorian (Florian Pelz)
2019-11-06 13:53 ` Python package naming: Dots vs hyphens Tobias Geerinckx-Rice
2019-11-10 10:57 ` Andreas Enge
2019-11-11 9:30 ` Efraim Flashner
2019-11-11 10:24 ` pelzflorian (Florian Pelz)
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=20191106071917.GJ14453@E5400 \
--to=efraim@flashner.co.il \
--cc=guix-devel@gnu.org \
--cc=pelzflorian@pelzflorian.de \
--cc=pjotr2019@thebird.nl \
/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).