commit: 6f4a61605dbb953ae325bfe0b63896e62c259616 Author: Andrew Ammerlaan <andrewammerlaan <AT> gentoo <DOT> org> AuthorDate: Mon Mar 27 17:27:55 2023 +0000 Commit: Andrew Ammerlaan <andrewammerlaan <AT> gentoo <DOT> org> CommitDate: Mon Mar 27 17:27:55 2023 +0000 URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=6f4a6160
dev-python/trio-asyncio: treeclean Closes: https://bugs.gentoo.org/888444 Closes: https://bugs.gentoo.org/896898 Signed-off-by: Andrew Ammerlaan <andrewammerlaan <AT> gentoo.org> dev-python/trio-asyncio/Manifest | 1 - .../trio-asyncio/files/no-pytest-runner.patch | 10 ----- dev-python/trio-asyncio/metadata.xml | 28 -------------- .../trio-asyncio/trio-asyncio-0.12.0-r1.ebuild | 43 ---------------------- profiles/package.mask | 6 --- 5 files changed, 88 deletions(-) diff --git a/dev-python/trio-asyncio/Manifest b/dev-python/trio-asyncio/Manifest deleted file mode 100644 index bc3289b8e24d..000000000000 --- a/dev-python/trio-asyncio/Manifest +++ /dev/null @@ -1 +0,0 @@ -DIST trio-asyncio-0.12.0.gh.tar.gz 72508 BLAKE2B f2dad48e20dadb81f603f8e7edf5d108f5c1dec332e65599e06495a9e3b919d20a15e3cb0d4f06c46a0e844cd79a88c172043b5cae2bc632661679a9ac854c04 SHA512 da630bf95d0736efd419a7b84d3fcb55f4440ef5f3ac584f36b2eca9188145d4581b20d4842b1322b07f176822f7c76e32ae57ac71899ea2445ce1783bcd382c diff --git a/dev-python/trio-asyncio/files/no-pytest-runner.patch b/dev-python/trio-asyncio/files/no-pytest-runner.patch deleted file mode 100644 index 6eec59da4286..000000000000 --- a/dev-python/trio-asyncio/files/no-pytest-runner.patch +++ /dev/null @@ -1,10 +0,0 @@ ---- a/setup.py 2021-03-27 18:54:07.104800689 +0100 -+++ b/setup.py 2021-03-27 18:54:23.197091635 +0100 -@@ -77,7 +77,6 @@ - include_package_data=True, - python_requires=">=3.6", # temporary, for RTD - keywords=["async", "io", "trio", "asyncio", "trio-asyncio"], -- setup_requires=['pytest-runner'], - tests_require=['pytest >= 5.4', 'pytest-trio >= 0.6', 'outcome'], - classifiers=[ - "Development Status :: 4 - Beta", diff --git a/dev-python/trio-asyncio/metadata.xml b/dev-python/trio-asyncio/metadata.xml deleted file mode 100644 index 867a2587c7ff..000000000000 --- a/dev-python/trio-asyncio/metadata.xml +++ /dev/null @@ -1,28 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<!DOCTYPE pkgmetadata SYSTEM "https://www.gentoo.org/dtd/metadata.dtd";> - -<pkgmetadata> - <maintainer type="person"> - <email>[email protected]</email> - <name>Andrew Ammerlaan</name> - </maintainer> - <stabilize-allarches/> - <longdescription lang="en"> -Rationale - -Trio has native concepts of tasks and task cancellation. Asyncio is based on callbacks and chaining Futures, albeit with nicer syntax, which make handling of failures and timeouts fundamentally less reliable, especially in larger programs. Thus, you really want to base your async project on Trio. - -On the other hand, there are quite a few asyncio-enhanced libraries. You really don't want to re-invent any wheels in your project. - -Thus, being able to use asyncio libraries from Trio is useful. trio-asyncio enables you to do that, and more. -Transparent vs. explicit translation - -trio_asyncio does not try to magically allow calling await trio_code() from asyncio or vice versa. There are multiple reasons for this; the executive summary is that cross-domain calls can't be made to work correctly, and any such call is likely to result in an irrecoverable error. You need to keep your code's asyncio and trio domains rigidly separate. - -Fortunately, this is not difficult. - </longdescription> - <upstream> - <remote-id type="github">python-trio/trio-asyncio</remote-id> - <remote-id type="pypi">trio-asyncio</remote-id> - </upstream> -</pkgmetadata> diff --git a/dev-python/trio-asyncio/trio-asyncio-0.12.0-r1.ebuild b/dev-python/trio-asyncio/trio-asyncio-0.12.0-r1.ebuild deleted file mode 100644 index 70c480643dd7..000000000000 --- a/dev-python/trio-asyncio/trio-asyncio-0.12.0-r1.ebuild +++ /dev/null @@ -1,43 +0,0 @@ -# Copyright 1999-2023 Gentoo Authors -# Distributed under the terms of the GNU General Public License v2 - -EAPI=8 - -PYTHON_COMPAT=( python3_{9..10} ) -DISTUTILS_USE_PEP517=setuptools -inherit distutils-r1 - -DESCRIPTION="a re-implementation of the asyncio mainloop on top of Trio" -HOMEPAGE=" - https://github.com/python-trio/trio-asyncio - https://pypi.org/project/trio-asyncio/ -" -SRC_URI="https://github.com/python-trio/${PN}/archive/v${PV}.tar.gz -> ${P}.gh.tar.gz" - -LICENSE="|| ( Apache-2.0 MIT )" -SLOT="0" -KEYWORDS="~amd64" - -RDEPEND=" - dev-python/outcome[${PYTHON_USEDEP}] - dev-python/sniffio[${PYTHON_USEDEP}] - >=dev-python/trio-0.15.0[${PYTHON_USEDEP}] -" -BDEPEND=" - test? ( - >=dev-python/pytest-trio-0.6[${PYTHON_USEDEP}] - ) -" -PATCHES=( "${FILESDIR}/no-pytest-runner.patch" ) - -EPYTEST_DESELECT=( - # RuntimeError: You're within a Trio environment. - # https://bugs.gentoo.org/834955 - /Python-3.8/test_asyncio/test_locks.py::ConditionTests::test_ambiguo - /Python-3.9/test_asyncio/test_locks.py::ConditionTests::test_ambiguo - /Python-3.10/test_asyncio/test_locks.py::ConditionTests::test_ambiguo - /Python-3.11/test_asyncio/test_locks.py::ConditionTests::test_ambiguo -) - -distutils_enable_tests pytest -distutils_enable_sphinx docs/source dev-python/sphinxcontrib-trio dev-python/sphinx-rtd-theme diff --git a/profiles/package.mask b/profiles/package.mask index 532cc16525e1..95a0672273ea 100644 --- a/profiles/package.mask +++ b/profiles/package.mask @@ -251,12 +251,6 @@ sys-power/dptfxtract gnome-extra/seahorse-nautilus x11-libs/libcryptui -# Andrew Ammerlaan <[email protected]> (2023-02-25) -# Fails tests, last upstream commit 2021, does not work with -# python3.11. No reverse dependencies. -# Removal on 2023-03-27. Bug 896898 and 888444 -dev-python/trio-asyncio - # Ben Kohler <[email protected]> (2023-01-30) # Breaks too many revdeps for now =app-text/discount-3*
