From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: python3-pep517-0.9.1
Date: Thu, 18 Feb 2021 19:38:49 +0100 [thread overview]
Message-ID: <20210218183849.l2pGhJ1GXIpVtI2vEcxt5ovKU9tfXsCCNlRe5utFzFo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28843@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 725 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/pull/28843#issuecomment-781553959
Comment:
What is the value of this package? PEP-517 still seems to be in flux. Pip seems to be the only viable builder and installer right now. The nascent "build" and "install" packages may eventually provide a lightweight alternative good for distribution packagers, but they aren't there yet. The build backends are currently so fragmented that it seems like every project that walks away from setuptools winds up choosing a different backend.
If this doesn't satisfy a dependency for something, I'm hesitant to pull it in when, for all we know, it will be *de facto* useless in a year.
next prev parent reply other threads:[~2021-02-18 18:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-18 15:19 [PR PATCH] " paper42
2021-02-18 15:42 ` [PR PATCH] [Updated] " paper42
2021-02-18 16:08 ` [PR REVIEW] " ericonr
2021-02-18 16:21 ` [PR PATCH] [Updated] " paper42
2021-02-18 18:38 ` ahesford [this message]
2021-02-19 14:35 ` paper42
2021-02-22 14:18 ` [PR REVIEW] " ahesford
2021-02-22 14:18 ` ahesford
2021-02-22 14:24 ` ericonr
2021-02-22 14:29 ` ahesford
2021-03-02 20:00 ` [PR PATCH] [Updated] " paper42
2021-03-02 20:01 ` paper42
2021-03-12 13:50 ` [PR REVIEW] " ahesford
2021-03-12 19:47 ` [PR PATCH] [Updated] " paper42
2021-03-12 19:52 ` paper42
2021-03-15 11:55 ` ahesford
2021-03-16 21:06 ` paper42
2021-03-16 21:06 ` [PR PATCH] [Closed]: " paper42
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=20210218183849.l2pGhJ1GXIpVtI2vEcxt5ovKU9tfXsCCNlRe5utFzFo@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).