Date: Sat, 19 Dec 2020 20:04:01 +0000 (UTC) From: Sunpoet Po-Chuan Hsieh <sunpoet@FreeBSD.org> To: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: svn commit: r558474 - in head/devel: . py-nest-asyncio Message-ID: <202012192004.0BJK41J3094629@repo.freebsd.org>
next in thread | raw e-mail | index | archive | help
Author: sunpoet Date: Sat Dec 19 20:04:01 2020 New Revision: 558474 URL: https://svnweb.freebsd.org/changeset/ports/558474 Log: Add py-nest-asyncio 1.4.3 By design asyncio does not allow its event loop to be nested. This presents a practical problem: When in an environment where the event loop is already running it's impossible to run tasks and wait for the result. Trying to do so will give the error "RuntimeError: This event loop is already running". The issue pops up in various environments, such as web servers, GUI applications and in Jupyter notebooks. This module patches asyncio to allow nested use of asyncio.run and loop.run_until_complete. WWW: https://github.com/erdewit/nest_asyncio Added: head/devel/py-nest-asyncio/ head/devel/py-nest-asyncio/Makefile (contents, props changed) head/devel/py-nest-asyncio/distinfo (contents, props changed) head/devel/py-nest-asyncio/pkg-descr (contents, props changed) Modified: head/devel/Makefile Modified: head/devel/Makefile ============================================================================== --- head/devel/Makefile Sat Dec 19 20:03:55 2020 (r558473) +++ head/devel/Makefile Sat Dec 19 20:04:01 2020 (r558474) @@ -4644,6 +4644,7 @@ SUBDIR += py-nbconvert SUBDIR += py-nbdime SUBDIR += py-nbformat + SUBDIR += py-nest-asyncio SUBDIR += py-node-semver SUBDIR += py-nodeenv SUBDIR += py-nose Added: head/devel/py-nest-asyncio/Makefile ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ head/devel/py-nest-asyncio/Makefile Sat Dec 19 20:04:01 2020 (r558474) @@ -0,0 +1,22 @@ +# Created by: Po-Chuan Hsieh <sunpoet@FreeBSD.org> +# $FreeBSD$ + +PORTNAME= nest-asyncio +PORTVERSION= 1.4.3 +CATEGORIES= devel python +MASTER_SITES= CHEESESHOP +PKGNAMEPREFIX= ${PYTHON_PKGNAMEPREFIX} +DISTNAME= nest_asyncio-${PORTVERSION} + +MAINTAINER= sunpoet@FreeBSD.org +COMMENT= Patch asyncio to allow nested event loops + +LICENSE= BSD2CLAUSE +LICENSE_FILE= ${WRKSRC}/LICENSE + +USES= python:3.5+ +USE_PYTHON= autoplist concurrent distutils + +NO_ARCH= yes + +.include <bsd.port.mk> Added: head/devel/py-nest-asyncio/distinfo ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ head/devel/py-nest-asyncio/distinfo Sat Dec 19 20:04:01 2020 (r558474) @@ -0,0 +1,3 @@ +TIMESTAMP = 1608366070 +SHA256 (nest_asyncio-1.4.3.tar.gz) = eaa09ef1353ebefae19162ad423eef7a12166bcc63866f8bff8f3635353cd9fa +SIZE (nest_asyncio-1.4.3.tar.gz) = 5996 Added: head/devel/py-nest-asyncio/pkg-descr ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ head/devel/py-nest-asyncio/pkg-descr Sat Dec 19 20:04:01 2020 (r558474) @@ -0,0 +1,12 @@ +By design asyncio does not allow its event loop to be nested. This presents a +practical problem: When in an environment where the event loop is already +running it's impossible to run tasks and wait for the result. Trying to do so +will give the error "RuntimeError: This event loop is already running". + +The issue pops up in various environments, such as web servers, GUI applications +and in Jupyter notebooks. + +This module patches asyncio to allow nested use of asyncio.run and +loop.run_until_complete. + +WWW: https://github.com/erdewit/nest_asyncio
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?202012192004.0BJK41J3094629>