unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Vinicius Monego <monego@posteo.net>
To: Simon Tournier <zimon.toutoune@gmail.com>, 67642@debbugs.gnu.org
Subject: [bug#67642] [PATCH 2/5] gnu: Add hatch.
Date: Tue, 12 Mar 2024 21:15:10 +0000	[thread overview]
Message-ID: <02d29258-b178-4022-93c2-90673d714592@posteo.net> (raw)
In-Reply-To: <87jzmqm4lt.fsf@gmail.com>

Hi Simon,

Em 27/02/2024 10:14, Simon Tournier escreveu:
> Hi,
>
> On mar., 05 déc. 2023 at 15:21, Vinicius Monego <monego@posteo.net> wrote:
>
>> +(define-public hatch
>> +  (package
>> +    (name "hatch")
>> +    (version "1.7.0")
> Following a question in Café Guix, I am giving a look at this.  And I
> see that bug#58310 [1] has:
>
>          +    (name "python-hatch")
>          +    (version "1.10.0")
>
> It leads to two questions:
>
>   1. Why the just name “hatch” and not “python-hatch”?

I remember a convention to name applications without the python- prefix, 
it was only used for libraries. See the pre-commit, gunicorn, hypercorn 
packages for instance.

>
>   2. Why 1.7.0 and not 1.10.0 or higher?
>
>
> 1: [bug#58310] [PATCH 05/14] gnu: Add python-hatch.
> Garek Dyszel via Guix-patches via <guix-patches@gnu.org>
> Wed, 05 Oct 2022 13:46:04 -0400
> id:878rluqi3n.fsf@disroot.org
> https://issues.guix.gnu.org/58310
> https://issues.guix.gnu.org/msgid/878rluqi3n.fsf@disroot.org
> https://yhetil.org/guix/878rluqi3n.fsf@disroot.org
>
>
> Cheers,
> simon

Looking at the date (2022-10-05), that patch seems to introduce 
python-hatchling and not python-hatch. Hatchling 1.10.0 was released on 
2022-09-19. The latest version of Hatch is 1.9.4, which was released 17 
hours ago. Both packages are tagged in the same repository [1], but are 
distinct packages. Hatchling is the build backend while hatch is a 
Python project management tool.

Vinicius

[1] https://github.com/pypa/hatch/releases





  reply	other threads:[~2024-03-12 21:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-05 15:18 [bug#67642] [PATCH 0/5] Add some Python build-related packages Vinicius Monego
2023-12-05 15:21 ` [bug#67642] [PATCH 1/5] gnu: Add python-userpath Vinicius Monego
2023-12-05 15:21 ` [bug#67642] [PATCH 2/5] gnu: Add hatch Vinicius Monego
2024-02-27 13:14   ` Simon Tournier
2024-03-12 21:15     ` Vinicius Monego [this message]
2023-12-05 15:21 ` [bug#67642] [PATCH 3/5] gnu: Add python-pytest-subprocess Vinicius Monego
2023-12-05 15:21 ` [bug#67642] [PATCH 4/5] gnu: Add python-scikit-build-core Vinicius Monego
2023-12-05 15:21 ` [bug#67642] [PATCH 5/5] gnu: Add python-spin Vinicius Monego
2024-02-08  7:35 ` [bug#67642] [PATCH 0/5] Add some Python build-related packages obonnefon
2024-02-28  8:14 ` obonnefon
2024-05-22 18:16 ` [bug#67642] QA review for 67642 Nicolas Graves via Guix-patches via

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=02d29258-b178-4022-93c2-90673d714592@posteo.net \
    --to=monego@posteo.net \
    --cc=67642@debbugs.gnu.org \
    --cc=zimon.toutoune@gmail.com \
    /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).