From b7524220f5cc44d0d0c690b2bcb1f93872ab6188 Mon Sep 17 00:00:00 2001 From: Andrew Ammerlaan Date: Sun, 27 Jun 2021 17:37:59 +0200 Subject: [PATCH] dev-python/trio-asyncio: move to ::gentoo Signed-off-by: Andrew Ammerlaan --- dev-python/pytest-trio/Manifest | 1 - dev-python/pytest-trio/metadata.xml | 13 ----- .../pytest-trio/pytest-trio-0.7.0.ebuild | 55 ------------------- dev-python/trio-asyncio/Manifest | 1 - .../trio-asyncio/files/no-pytest-runner.patch | 10 ---- dev-python/trio-asyncio/metadata.xml | 27 --------- .../trio-asyncio/trio-asyncio-0.12.0.ebuild | 36 ------------ 7 files changed, 143 deletions(-) delete mode 100644 dev-python/pytest-trio/Manifest delete mode 100644 dev-python/pytest-trio/metadata.xml delete mode 100644 dev-python/pytest-trio/pytest-trio-0.7.0.ebuild delete mode 100644 dev-python/trio-asyncio/Manifest delete mode 100644 dev-python/trio-asyncio/files/no-pytest-runner.patch delete mode 100644 dev-python/trio-asyncio/metadata.xml delete mode 100644 dev-python/trio-asyncio/trio-asyncio-0.12.0.ebuild diff --git a/dev-python/pytest-trio/Manifest b/dev-python/pytest-trio/Manifest deleted file mode 100644 index e39be86a7c..0000000000 --- a/dev-python/pytest-trio/Manifest +++ /dev/null @@ -1 +0,0 @@ -DIST pytest-trio-0.7.0.tar.gz 47784 BLAKE2B 59b28df45e87804e0b6eb557a0cf259fdc3636cc7a03d78248fb814d55904ed01d00a530b194b2bfe93ccfb9de528d70a372faf1f6db24531c230319122db2e5 SHA512 547036c94f33cf8e755c88d608c5fddfa5c583fdaa7e604598d470e250a006c571702a81bac4f273b74450a8c10e4be404bad74d4104403fe1c9c70e872dff53 diff --git a/dev-python/pytest-trio/metadata.xml b/dev-python/pytest-trio/metadata.xml deleted file mode 100644 index 0cc4d7f61e..0000000000 --- a/dev-python/pytest-trio/metadata.xml +++ /dev/null @@ -1,13 +0,0 @@ - - - - - co-maintainers welcome - lssndrbarbieri@gmail.com - Alessandro Barbieri - - - python-trio/pytest-trio - pytest-trio - - diff --git a/dev-python/pytest-trio/pytest-trio-0.7.0.ebuild b/dev-python/pytest-trio/pytest-trio-0.7.0.ebuild deleted file mode 100644 index a56157c2fb..0000000000 --- a/dev-python/pytest-trio/pytest-trio-0.7.0.ebuild +++ /dev/null @@ -1,55 +0,0 @@ -# Copyright 1999-2021 Gentoo Authors -# Distributed under the terms of the GNU General Public License v2 - -EAPI="7" - -PYTHON_COMPAT=( python3_{7,8,9} ) -DISTUTILS_USE_SETUPTOOLS=bdepend -DOCS_BUILDER="sphinx" -DOCS_DIR="${S}/docs/source" -DOCS_DEPEND=" - >=dev-python/attrs-17.4.0 - >=dev-python/sphinx-1.6.1 - dev-python/sphinx_rtd_theme - dev-python/sphinxcontrib-trio -" - -inherit distutils-r1 docs - -DESCRIPTION="This is a pytest plugin to help you test projects that use Trio" -HOMEPAGE=" - https://github.com/python-trio/pytest-trio - https://pypi.org/project/pytest-trio -" -SRC_URI="mirror://pypi/${P:0:1}/${PN}/${P}.tar.gz" - -LICENSE="|| ( MIT Apache-2.0 )" -SLOT="0" -KEYWORDS="~amd64" -#too many errors -RESTRICT="test" - -RDEPEND=" - >=dev-python/async_generator-1.9[${PYTHON_USEDEP}] - dev-python/outcome[${PYTHON_USEDEP}] - >=dev-python/trio-0.15[${PYTHON_USEDEP}] -" -DEPEND=" - ${RDEPEND} - test? ( - >=dev-python/hypothesis-3.64[${PYTHON_USEDEP}] - = 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 f34dda2d3e..0000000000 --- a/dev-python/trio-asyncio/metadata.xml +++ /dev/null @@ -1,27 +0,0 @@ - - - - - - lssndrbarbieri@gmail.com - Alessandro Barbieri - - -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. - - - python-trio/trio-asyncio - trio-asyncio - - diff --git a/dev-python/trio-asyncio/trio-asyncio-0.12.0.ebuild b/dev-python/trio-asyncio/trio-asyncio-0.12.0.ebuild deleted file mode 100644 index ac86ace5e5..0000000000 --- a/dev-python/trio-asyncio/trio-asyncio-0.12.0.ebuild +++ /dev/null @@ -1,36 +0,0 @@ -# Copyright 1999-2021 Gentoo Authors -# Distributed under the terms of the GNU General Public License v2 - -EAPI=7 - -PYTHON_COMPAT=( python3_{7,8,9} ) - -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}.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}] -" -DEPEND=" - ${RDEPEND} - test? ( - >=dev-python/pytest-5.4[${PYTHON_USEDEP}] - >=dev-python/pytest-trio-0.6[${PYTHON_USEDEP}] - ) -" -PATCHES=( "${FILESDIR}/no-pytest-runner.patch" ) - -distutils_enable_tests pytest -distutils_enable_sphinx docs/source dev-python/sphinxcontrib-trio