From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/3] btrfs-progs: libbtrfsutil/python: fix all the warnings
Date: Sat, 21 Sep 2024 11:56:23 +0930 [thread overview]
Message-ID: <cover.1726885304.git.wqu@suse.com> (raw)
There are the following warnings when building the python binding the
proper way (directly calling "setup.py build" is no longer recommended):
$ python -m build btrfs-progs/libbtrfsutil/python
* Creating isolated environment: venv+pip...
* Installing packages in isolated environment:
- setuptools >= 40.8.0
* Getting build dependencies for sdist...
/tmp/build-env-2u6q_udl/lib/python3.12/site-packages/setuptools/_distutils/extension.py:139: UserWarning: Unknown Extension options: 'headers'
warnings.warn(msg)
* Building sdist...
/tmp/build-env-2u6q_udl/lib/python3.12/site-packages/setuptools/_distutils/extension.py:139: UserWarning: Unknown Extension options: 'headers'
warnings.warn(msg)
writing manifest file 'btrfsutil.egg-info/SOURCES.txt'
warning: sdist: standard file not found: should have one of README, README.rst, README.txt, README.md
This patch fixes them by:
- Use MANIFEST.in to properly include the "btrfsutilpy.h"
- Remove unnecessary build options for C files
- Reuse the existing README.md by a softlink
So that even in a virtual environment the README.md will still be
properly copied.
TODO: Migrate the "python setup.py build" system to "python -m build"
for building and tox for tests.
Qu Wenruo (3):
btrfs-progs: libbtrfsutil/python: use MANIFEST.in for headers
btrfs-progs: libbtrfsutil/python: remove unnecessary build options
btrfs-progs: libbtrfsutil/python: reuse existing README.md for long
description
libbtrfsutil/python/MANIFEST.in | 1 +
libbtrfsutil/python/README.md | 1 +
libbtrfsutil/python/setup.py | 7 ++-----
3 files changed, 4 insertions(+), 5 deletions(-)
create mode 100644 libbtrfsutil/python/MANIFEST.in
create mode 120000 libbtrfsutil/python/README.md
--
2.46.1
next reply other threads:[~2024-09-21 2:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-21 2:26 Qu Wenruo [this message]
2024-09-21 2:26 ` [PATCH 1/3] btrfs-progs: libbtrfsutil/python: use MANIFEST.in for headers Qu Wenruo
2024-09-21 2:26 ` [PATCH 2/3] btrfs-progs: libbtrfsutil/python: remove unnecessary build options Qu Wenruo
2024-09-21 2:26 ` [PATCH 3/3] btrfs-progs: libbtrfsutil/python: reuse existing README.md for long description Qu Wenruo
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=cover.1726885304.git.wqu@suse.com \
--to=wqu@suse.com \
--cc=linux-btrfs@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;
as well as URLs for NNTP newsgroup(s).