From: GitHub issues - opened <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: 1.2.14: SetuptoolsDeprecationWarning due to the use of `sys.exit(0)`
Date: Tue, 15 Apr 2025 09:18:10 +0200 (CEST) [thread overview]
Message-ID: <18366cc26eb87000-webhooks-bot@alsa-project.org> (raw)
In-Reply-To: <18366cc26db3cf00-webhooks-bot@alsa-project.org>
alsa-project/alsa-python issue #18 was opened from dvzrv:
Hi! 👋
I package this project for Arch Linux.
During update to 1.2.14 I noticed that setuptools now raises the following warning:
```
/usr/lib/python3.13/site-packages/setuptools/build_meta.py:522: SetuptoolsDeprecationWarning: Running `setup.py` directly as CLI tool is deprecated.
!!
********************************************************************************
Please avoid using `sys.exit(0)` or similar statements that don't fit in the paradigm of a configuration file.
See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html for details.
********************************************************************************
!!
super().run_setup(setup_script=setup_script)
```
This appears to be triggered by the `sys.exit(0)` call in setup.py:
https://github.com/alsa-project/alsa-python/blob/20b2b3999f24af462815b9c86e967643ccd30037/setup.py#L74-L75
(Setuptools now offers one of the various PEP517 build backends and calling setup.py directly as a script is deprecated).
Looking at the file I noticed that there are still conditionals that accommodate Python2:
https://github.com/alsa-project/alsa-python/blob/20b2b3999f24af462815b9c86e967643ccd30037/setup.py#L77-L80
Those should be removed, as the script itself is marked as Python3 (and well of course because Python2 is long discontinued 😅).
Issue URL : https://github.com/alsa-project/alsa-python/issues/18
Repository URL: https://github.com/alsa-project/alsa-python
parent reply other threads:[~2025-04-15 7:18 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <18366cc26db3cf00-webhooks-bot@alsa-project.org>]
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=18366cc26eb87000-webhooks-bot@alsa-project.org \
--to=github@alsa-project.org \
--cc=alsa-devel@alsa-project.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