From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Revert "python3-poetry-core: update to 1.3.1."
Date: Fri, 07 Oct 2022 14:11:40 +0200 [thread overview]
Message-ID: <20221007121140.48PjoQaEgfZLcQv5nhDteL64z2mOCgHwi1dlXX4Ul7U@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39777@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1029 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/pull/39777#issuecomment-1271510872
Comment:
I apologize; my comment was a bit harsh.
The underlying problem is the fragmented and constantly changing official view of Python packaging building and distribution. PyPA seems to take the view that only pip matters, but they haven't addressed the first half of the packaging problem adequately and pip is a terrible package manager. The `search` sub-command has been broken by design for years because they don't seem to know how to rate-limit spammy queries; at this point why does it still exist? Even worse, why does the package manager happily let you install entirely new dependency chains and only **after** the fact warn you about conflicting version restrictions?
It's only natural that each project tries to work around a sea of inconsistent and half-formed tooling with unique hacks, but that just causes problems elsewhere. Damned whether you do or don't, indeed.
next prev parent reply other threads:[~2022-10-07 12:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-06 17:29 [PR PATCH] " icp1994
2022-10-06 17:41 ` ahesford
2022-10-06 17:51 ` icp1994
2022-10-06 18:04 ` ahesford
2022-10-06 18:12 ` icp1994
2022-10-06 19:10 ` ahesford
2022-10-07 11:38 ` reivilibre
2022-10-07 12:11 ` ahesford [this message]
2022-10-07 13:20 ` reivilibre
2022-10-07 14:33 ` [PR PATCH] [Closed]: " ahesford
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=20221007121140.48PjoQaEgfZLcQv5nhDteL64z2mOCgHwi1dlXX4Ul7U@z \
--to=ahesford@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).