From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: python3-pep517-0.9.1
Date: Mon, 15 Mar 2021 12:55:42 +0100 [thread overview]
Message-ID: <20210315115542.SZmUTgHkROfIdy7eMEXruvf1TvgtBfBROGFSYcKzFFg@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: 733 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/pull/28843#issuecomment-799360276
Comment:
I wonder if this is still relevant to you. The `pep517.build` module you reference is deprecated: https://github.com/pypa/pep517/pull/83 and the author recommends the `build` module instead. Even the link you referenced for setuptools suggests using the `build` module now: https://setuptools.readthedocs.io/en/latest/userguide/quickstart.html#id5
It is this kind of constant churn that gives me pause about the whole pep517 mechanism. The Python people can't figure out what they want to do, they just know it's Better™. Meanwhile, we add package maintenance burden chasing after them.
next prev parent reply other threads:[~2021-03-15 11:55 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
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 [this message]
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=20210315115542.SZmUTgHkROfIdy7eMEXruvf1TvgtBfBROGFSYcKzFFg@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).