From: Tanguy LE CARROUR <tanguy@bioneland.org>
To: Antero Mejr <mail@antr.me>, 71540@debbugs.gnu.org
Cc: me@bonfacemunyoki.com, sharlatanus@gmail.com, lars@6xq.net,
jgart@dismail.de, marius@gnu.org
Subject: [bug#71540] [PATCH 0/5] gnu: poetry: Update to 1.7.1.
Date: Fri, 14 Jun 2024 10:33:19 +0200 [thread overview]
Message-ID: <171835399913.15842.9755585658776807966@bioneland.org> (raw)
In-Reply-To: <877cesu09g.fsf@antr.me>
Hi,
Quoting Antero Mejr (2024-06-13 21:10:35)
> Updating to 1.7.1 instead of the latest, because poetry 1.8.2 requires a
> newer python-packaging, which would trigger many rebuilds.
>
> Antero Mejr (5):
> gnu: Add python-installer.
> gnu: Add python-rapidfuzz.
> gnu: Add python-poetry-core-next.
> gnu: python-cleo: Update to 2.1.0.
> gnu: poetry: Update to 1.7.1.
>
> gnu/packages/python-build.scm | 12 +++
> gnu/packages/python-xyz.scm | 144 ++++++++++++++++++++++++++++------
> 2 files changed, 131 insertions(+), 25 deletions(-)
Thanks for working on this!
>> Updating to 1.7.1 instead of the latest, because poetry 1.8.2 requires a
>> newer python-packaging, which would trigger many rebuilds.a
> How about to apply patches against python-team branch with the latest version?
As Oleg said, it would be great to have version 1.8.2. I have to confess that,
because it’s not available in Guix, I’ve been installing it using pipx for few
months now.
This being said here are some (useless) remarks…
- gnu: Add python-installer.
* The synopsis is different from the others. It starts with a "A" and ends with a "."
- gnu: Add python-poetry-plugin-export.
* The package name used in `pypi-uri` contains "_" where I usually see "-".
Is that on purpose?
- gnu: Add python-poetry-plugin-export-minimal.
* LGTM
- gnu: Add python-rapidfuzz.
* LGTM
- gnu: Add python-poetry-core-next.
* The package name used in `pypi-uri` contains "_" where I usually see "-".
- gnu: python-cleo: Update to 2.1.0.
* There is no mention of the `snippet` in the commit message. Wouldn’t it be
worth explaining?
- gnu: poetry: Update to 1.7.1.
* There is no mention to the fact that you enabled some tests that were
previously altogether disabled. Which is good IMHO! 👍
But the most important is that it builds and it works! Thanks!
--
Tanguy
next prev parent reply other threads:[~2024-06-14 8:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-13 19:10 [bug#71540] [PATCH 0/5] gnu: poetry: Update to 1.7.1 Antero Mejr
2024-06-13 19:25 ` [bug#71540] [PATCH 1/7] gnu: Add python-installer Antero Mejr
2024-06-13 19:26 ` [bug#71540] [PATCH 2/7] gnu: Add python-poetry-plugin-export Antero Mejr
2024-06-13 19:27 ` [bug#71540] [PATCH 3/7] gnu: Add python-poetry-plugin-export-minimal Antero Mejr
2024-06-13 19:27 ` [bug#71540] [PATCH 4/7] gnu: Add python-rapidfuzz Antero Mejr
2024-06-13 19:28 ` [bug#71540] [PATCH 5/7] gnu: Add python-poetry-core-next Antero Mejr
2024-06-13 19:28 ` [bug#71540] [PATCH 6/7] gnu: python-cleo: Update to 2.1.0 Antero Mejr
2024-06-13 19:29 ` [bug#71540] [PATCH 7/7] gnu: poetry: Update to 1.7.1 Antero Mejr
2024-06-13 22:34 ` [bug#71540] [PATCH 0/5] " Sharlatan Hellseher
2024-06-14 8:33 ` Tanguy LE CARROUR [this message]
2024-06-14 20:55 ` Antero Mejr
2024-06-17 6:54 ` Tanguy LE CARROUR
2024-06-17 16:04 ` Tanguy LE CARROUR
2024-06-14 20:41 ` [bug#71540] [PATCH 1/8] gnu: Add python-installer Antero Mejr
2024-06-14 20:42 ` [bug#71540] [PATCH 2/8] gnu: Add python-poetry-plugin-export Antero Mejr
2024-06-14 20:47 ` [bug#71540] [PATCH 3/8] gnu: python-poetry-core: Update to 1.9.0 Antero Mejr
2024-06-14 20:48 ` [bug#71540] [PATCH 4/8] gnu: poetry: Update to 1.8.3 Antero Mejr
2024-06-14 20:48 ` [bug#71540] [PATCH 5/8] gnu: python-betamax: Update to 0.9.0 Antero Mejr
2024-06-14 20:48 ` [bug#71540] [PATCH 6/8] gnu: python-requests-toolbelt: Update to 1.0.0 Antero Mejr
2024-06-14 20:49 ` [bug#71540] [PATCH 7/8] gnu: python-jsonpickle: Update to 3.2.1 Antero Mejr
2024-06-14 20:49 ` [bug#71540] [PATCH 8/8] gnu: Remove python-poetry-core-1.0 Antero Mejr
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=171835399913.15842.9755585658776807966@bioneland.org \
--to=tanguy@bioneland.org \
--cc=71540@debbugs.gnu.org \
--cc=jgart@dismail.de \
--cc=lars@6xq.net \
--cc=mail@antr.me \
--cc=marius@gnu.org \
--cc=me@bonfacemunyoki.com \
--cc=sharlatanus@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).