unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Ian Eure <ian@retrospec.tv>
To: 74889@debbugs.gnu.org
Cc: Ian Eure <ian@retrospec.tv>
Subject: [bug#74889] [PATCH] doc: Document use of setuptools with pyproject-build-system.
Date: Sun, 15 Dec 2024 09:51:12 -0800	[thread overview]
Message-ID: <20241215175129.30475-1-ian@retrospec.tv> (raw)

Add documentation for required native-inputs for building setup.py-based
Python projects with pyproject-build-system.  Remove mention of 2024, since
there are only two weeks left.

* dox/guix.texi (Build Systems): Document use of setuptools with
pyproject-build-system.

Change-Id: Ia5cba05033d84b808419456d8da09ff87bec3bb8
---
 doc/guix.texi | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/doc/guix.texi b/doc/guix.texi
index 3d501a08c9..cd80104eb4 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -9950,9 +9950,13 @@ It is considered ``experimental'' in that the implementation details are
 not set in stone yet, however users are encouraged to try it for new
 Python projects (even those using @file{setup.py}).  The API is subject to
 change, but any breaking changes in the Guix channel will be dealt with.
+Building @file{setup.py}-based Python projects requires adding the
+@code{python-setuptools} and @code{python-wheel} (from the
+@code{(gnu packages python-build)} module) packages to the package’s
+@code{native-inputs}.
 
 Eventually this build system will be deprecated and merged back into
-@var{python-build-system}, probably some time in 2024.
+@var{python-build-system}.
 @end defvar
 
 @defvar perl-build-system
-- 
2.46.0





             reply	other threads:[~2024-12-15 17:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-15 17:51 Ian Eure [this message]
2024-12-16 20:38 ` [bug#74889] [PATCH] doc: Document use of setuptools with pyproject-build-system Sharlatan Hellseher

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=20241215175129.30475-1-ian@retrospec.tv \
    --to=ian@retrospec.tv \
    --cc=74889@debbugs.gnu.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.
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).