From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/pyaudio/
Date: Sat, 30 Mar 2024 15:28:50 +0000 (UTC) [thread overview]
Message-ID: <1711811003.4181748b5a4b07f14272267ba741b0b2b82ec8e4.mgorny@gentoo> (raw)
commit: 4181748b5a4b07f14272267ba741b0b2b82ec8e4
Author: Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Sat Mar 30 15:03:23 2024 +0000
Commit: Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Sat Mar 30 15:03:23 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4181748b
dev-python/pyaudio: Remove old
Signed-off-by: Michał Górny <mgorny <AT> gentoo.org>
dev-python/pyaudio/pyaudio-0.2.13-r1.ebuild | 38 -----------------------------
1 file changed, 38 deletions(-)
diff --git a/dev-python/pyaudio/pyaudio-0.2.13-r1.ebuild b/dev-python/pyaudio/pyaudio-0.2.13-r1.ebuild
deleted file mode 100644
index 012803c8853a..000000000000
--- a/dev-python/pyaudio/pyaudio-0.2.13-r1.ebuild
+++ /dev/null
@@ -1,38 +0,0 @@
-# Copyright 1999-2023 Gentoo Authors
-# Distributed under the terms of the GNU General Public License v2
-
-EAPI=8
-
-PYTHON_COMPAT=( python3_{10..11} )
-PYPI_NO_NORMALIZE=1
-PYPI_PN="PyAudio"
-DISTUTILS_EXT=1
-DISTUTILS_USE_PEP517="setuptools"
-inherit distutils-r1 pypi
-
-DESCRIPTION="Python bindings for PortAudio"
-HOMEPAGE="https://people.csail.mit.edu/hubert/pyaudio/"
-
-LICENSE="MIT"
-SLOT="0"
-KEYWORDS="amd64 x86"
-
-# Tests work if you have the correct HW device(s) to test. 0.2.11-r1.
-RESTRICT="test"
-
-RDEPEND="media-libs/portaudio"
-DEPEND="${RDEPEND}"
-BDEPEND="test? ( dev-python/numpy[${PYTHON_USEDEP}] )"
-
-distutils_enable_sphinx sphinx
-distutils_enable_tests unittest
-
-python_test() {
- elog "These tests require an OS loopback sound device that forwards audio"
- elog "output, generated by PyAudio for playback, and forwards it to an input"
- elog "device, which PyAudio can record and verify against a test signal."
-
- cd tests || die
- # pyaudio_tests have very complicated runtime requirements, therefore skipping them.
- "${EPYTHON}" -m unittest error_tests -v || die "Tests fail with ${EPYTHON}"
-}
next reply other threads:[~2024-03-30 15:28 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-30 15:28 Michał Górny [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-30 14:59 [gentoo-commits] repo/gentoo:master commit in: dev-python/pyaudio/ Michał Górny
2024-03-30 14:59 Michał Górny
2024-03-14 11:25 Michał Górny
2023-09-12 6:25 Michał Górny
2023-09-11 18:36 Sam James
2023-09-11 12:36 Sam James
2023-08-11 7:29 Joonas Niilola
2023-08-11 7:29 Joonas Niilola
2023-08-11 7:29 Joonas Niilola
2023-04-08 11:16 Arthur Zamarin
2023-04-08 9:43 Arthur Zamarin
2023-03-08 14:13 Joonas Niilola
2022-08-03 9:10 Michał Górny
2022-08-03 6:25 Joonas Niilola
2022-08-02 20:27 Sam James
2021-11-01 8:29 Arthur Zamarin
2021-06-01 11:44 Sam James
2020-08-05 15:10 Michał Górny
2020-06-08 7:46 Joonas Niilola
2020-06-08 7:46 Joonas Niilola
2020-06-08 7:46 Joonas Niilola
2020-05-13 13:58 Joonas Niilola
2020-04-26 6:49 Michał Górny
2020-02-05 19:12 Michał Górny
2017-09-17 21:09 Matt Turner
2017-07-15 17:25 Tobias Klausmann
2017-05-02 15:15 Michał Górny
2017-04-29 20:22 Sebastian Pipping
2016-02-19 12:46 Patrick Lauer
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=1711811003.4181748b5a4b07f14272267ba741b0b2b82ec8e4.mgorny@gentoo \
--to=mgorny@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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