public inbox for linux-gpio@vger.kernel.org
 help / color / mirror / Atom feed
From: Vincent Fazio <vfazio@gmail.com>
To: linux-gpio@vger.kernel.org
Cc: Vincent Fazio <vfazio@gmail.com>
Subject: [libgpiod][PATCH 2/9] bindings: python: build_tests: simplify the Distribution
Date: Tue, 31 Mar 2026 19:14:51 -0500	[thread overview]
Message-ID: <20260401001459.19159-2-vfazio@gmail.com> (raw)
In-Reply-To: <20260401001459.19159-1-vfazio@gmail.com>

The version, package, and platform information is not necessary to
compile and stage the extensions, so drop that information.

If we need to add it back, we can use `dist.parse_config_files()` to
parse information from the pyproject.toml.

Signed-off-by: Vincent Fazio <vfazio@gmail.com>
---
 bindings/python/build_tests.py | 6 ------
 1 file changed, 6 deletions(-)

diff --git a/bindings/python/build_tests.py b/bindings/python/build_tests.py
index 6375b29..77e38ba 100644
--- a/bindings/python/build_tests.py
+++ b/bindings/python/build_tests.py
@@ -27,9 +27,6 @@ logging.configure()
 TOP_SRCDIR = getenv("TOP_SRCDIR", "../../")
 TOP_BUILDDIR = getenv("TOP_BUILDDIR", "../../")
 
-# __version__
-with open("gpiod/version.py", "r") as fd:
-    exec(fd.read())
 
 # The tests are run in-place with PYTHONPATH set to bindings/python
 # so we need the gpiod extension module too.
@@ -72,10 +69,7 @@ system_ext = Extension(
 
 dist = Distribution(
     {
-        "name": "gpiod",
         "ext_modules": [gpiosim_ext, system_ext, gpiod_ext],
-        "version": __version__,
-        "platforms": ["linux"],
     }
 )
 
-- 
2.43.0


  reply	other threads:[~2026-04-01  0:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-01  0:14 [libgpiod][PATCH 1/9] bindings: python: build_tests: do not fallback to distutils Vincent Fazio
2026-04-01  0:14 ` Vincent Fazio [this message]
2026-04-01  0:14 ` [libgpiod][PATCH 3/9] bindings: python: setup: add type annotations Vincent Fazio
2026-04-01  0:14 ` [libgpiod][PATCH 4/9] bindings: python: setup: apply linter recommendations Vincent Fazio
2026-04-01  0:14 ` [libgpiod][PATCH 5/9] bindings: python: setup: use logging module Vincent Fazio
2026-04-01  0:14 ` [libgpiod][PATCH 6/9] bindings: python: examples: add type annotations Vincent Fazio
2026-04-01  0:14 ` [libgpiod][PATCH 7/9] bindings: python: examples: apply linter recommendations Vincent Fazio
2026-04-01  0:14 ` [libgpiod][PATCH 8/9] bindings: python: add a lint dependency group Vincent Fazio
2026-04-01  0:14 ` [libgpiod][PATCH 9/9] bindings: python: update linter configuration Vincent Fazio
2026-04-02 14:37   ` Bartosz Golaszewski
2026-04-02 15:55     ` Vincent Fazio
2026-04-02 16:42       ` Bartosz Golaszewski
2026-04-02 17:01         ` Vincent Fazio
2026-04-03  9:02           ` Bartosz Golaszewski
2026-04-03 13:09             ` Vincent Fazio
2026-04-03  9:01 ` [libgpiod][PATCH 1/9] bindings: python: build_tests: do not fallback to distutils Bartosz Golaszewski

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=20260401001459.19159-2-vfazio@gmail.com \
    --to=vfazio@gmail.com \
    --cc=linux-gpio@vger.kernel.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