From: TinfoilSubmarine <TinfoilSubmarine@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: python3-py7zr: update to 0.18.3.
Date: Fri, 08 Apr 2022 03:35:14 +0200 [thread overview]
Message-ID: <20220408013514.3gLQFH69GK5vUfedL3XXFCq85dZE6cCDxgpG2eoPUes@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36538@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 751 bytes --]
New comment by TinfoilSubmarine on void-packages repository
https://github.com/void-linux/void-packages/pull/36538#issuecomment-1092354951
Comment:
> Both `python3-pybcj` and `python3-zipfile-deflate64` warn that testing via `setup.py` is deprecated and don't actually run tests. Can these be moved to `python3-pytest`? If not, just disable checks in those templates.
Running with pytest enables some tests for pybcj, but zipfile-deflate64 is...different. The tests aren't included in the source distribution from PyPi, so I tried switching to the GitHub source. Unfortunately, the package uses a zlib submodule and uses an internal zlib header file (zutil.h) not available in zlib-devel. So I think for now I will just skip tests on this one.
next prev parent reply other threads:[~2022-04-08 1:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-05 18:11 [PR PATCH] " TinfoilSubmarine
2022-04-07 13:58 ` [PR REVIEW] " ahesford
2022-04-07 13:58 ` ahesford
2022-04-08 1:18 ` TinfoilSubmarine
2022-04-08 1:35 ` TinfoilSubmarine [this message]
2022-04-08 1:37 ` [PR PATCH] [Updated] " TinfoilSubmarine
2022-04-08 1:39 ` [PR REVIEW] " TinfoilSubmarine
2022-04-08 1:40 ` [PR PATCH] [Updated] " TinfoilSubmarine
2022-04-11 15:03 ` TinfoilSubmarine
2022-04-12 11:25 ` TinfoilSubmarine
2022-04-12 11:36 ` TinfoilSubmarine
2022-04-12 11:36 ` [PR REVIEW] " TinfoilSubmarine
2022-04-14 16:02 ` [PR PATCH] [Closed]: " ahesford
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=20220408013514.3gLQFH69GK5vUfedL3XXFCq85dZE6cCDxgpG2eoPUes@z \
--to=tinfoilsubmarine@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).