From: eli-schwartz <eli-schwartz@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] New package: giara-1.0.1
Date: Mon, 10 Apr 2023 18:27:40 +0200 [thread overview]
Message-ID: <20230410162740.pYj5XtGtBB1v2tazqaH7CYCXAukzVwviMbliBKizBdc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37132@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1559 bytes --]
New review comment by eli-schwartz on void-packages repository
https://github.com/void-linux/void-packages/pull/37132#discussion_r1161871512
Comment:
> if there are no tests, they usually don't fail, so we don't have to disable them
Incorrect, the python3-module build style does this all the time, because it attempts to run `python3 setup.py test` regardless of whether tests exist. This command will:
- depend on all runtime dependencies, or attempt to install local copies of them with pip, but NOT all "extras" (optional) dependencies
- then import all source files (including the ones that have optional dependencies, which are not otherwise mentioned in the template since xbps does not support optional dependencies)
- then detect that there are zero tests, and not run them
And setuptools upstream has deprecated `setup.py test`, so any packages that actually used it (which was relatively uncommon, as people tend to prefer pytest or nose or whatever) have been busily porting away from it.
Incidentally, this: https://github.com/void-linux/void-packages/blob/0657a8bea7e6d89cff327e31949b5eebcb883952/common/build-style/python3-module.sh#L21-L23
is logically broken, because it is fallaciously incorrect to print a warning that "setup.py doesn't define a test command". That's not the role of setup.py to do -- the test command is defined globally in setuptools itself regardless of what a setup.py file does (a setup.py file can override the builtin one, the same way it can override the builtin "build_py" or "install" commands).
next prev parent reply other threads:[~2023-04-10 16:27 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-14 17:44 [PR PATCH] " jcgruenhage
2022-09-02 2:16 ` github-actions
2022-09-02 13:05 ` [PR PATCH] [Updated] " jcgruenhage
2022-09-02 13:05 ` jcgruenhage
2022-09-02 19:05 ` paper42
2022-09-03 8:25 ` [PR PATCH] [Updated] " jcgruenhage
2022-09-03 8:25 ` jcgruenhage
2022-11-27 10:58 ` [PR PATCH] [Updated] " jcgruenhage
2022-11-27 11:02 ` jcgruenhage
2022-12-11 20:44 ` [PR REVIEW] " paper42
2022-12-11 21:11 ` jcgruenhage
2022-12-11 21:41 ` jcgruenhage
2022-12-11 21:43 ` [PR PATCH] [Updated] " jcgruenhage
2022-12-11 21:57 ` [PR REVIEW] " paper42
2022-12-11 21:57 ` paper42
2022-12-11 21:57 ` paper42
2022-12-11 21:57 ` paper42
2022-12-11 21:57 ` paper42
2022-12-11 21:57 ` paper42
2022-12-11 21:57 ` paper42
2022-12-11 21:57 ` paper42
2022-12-11 23:30 ` jcgruenhage
2022-12-11 23:35 ` [PR PATCH] [Updated] " jcgruenhage
2022-12-16 18:58 ` [PR REVIEW] " paper42
2022-12-16 18:58 ` paper42
2022-12-16 23:01 ` [PR PATCH] [Updated] " jcgruenhage
2023-03-17 1:56 ` github-actions
2023-03-19 14:26 ` jcgruenhage
2023-04-10 16:27 ` eli-schwartz [this message]
2023-07-10 2:08 ` github-actions
2023-07-25 2:01 ` [PR PATCH] [Closed]: " github-actions
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=20230410162740.pYj5XtGtBB1v2tazqaH7CYCXAukzVwviMbliBKizBdc@z \
--to=eli-schwartz@users.noreply.github.com \
--cc=ml@inbox.vuxu.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).