All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Hilliard <james.hilliard1@gmail.com>
To: buildroot@buildroot.org
Cc: James Hilliard <james.hilliard1@gmail.com>
Subject: [Buildroot] [PATCH 1/1] utils/scanpypi: add missing setuptools fallback
Date: Wed,  9 Oct 2024 09:46:58 -0600	[thread overview]
Message-ID: <20241009154658.3777691-1-james.hilliard1@gmail.com> (raw)

Some projects use pyproject.toml without setting a build backend, per
pep517 we should simply fallback to using setuptools when no build
backend is specified.

Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
---
 utils/scanpypi | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/utils/scanpypi b/utils/scanpypi
index b6a2a92219..f47150ceb6 100755
--- a/utils/scanpypi
+++ b/utils/scanpypi
@@ -424,6 +424,9 @@ class BuildrootPackage():
                         self.setup_metadata['method'] = 'pep517'
                     else:
                         self.setup_metadata['method'] = 'unknown'
+            else:
+                self.build_backend = 'setuptools.build_meta'
+                self.setup_metadata = {'method': 'setuptools'}
         except FileNotFoundError:
             self.build_backend = 'setuptools.build_meta'
             self.setup_metadata = {'method': 'setuptools'}
-- 
2.34.1

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

             reply	other threads:[~2024-10-09 15:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-09 15:46 James Hilliard [this message]
2024-10-10 21:34 ` [Buildroot] [PATCH 1/1] utils/scanpypi: add missing setuptools fallback Thomas Petazzoni via buildroot

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=20241009154658.3777691-1-james.hilliard1@gmail.com \
    --to=james.hilliard1@gmail.com \
    --cc=buildroot@buildroot.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.