From owner-svn-ports-head@freebsd.org Sat Dec 19 20:04:02 2020 Return-Path: Delivered-To: svn-ports-head@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id EB5F24CEFF5; Sat, 19 Dec 2020 20:04:02 +0000 (UTC) (envelope-from sunpoet@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4CyxWk5cX7z4ZZP; Sat, 19 Dec 2020 20:04:02 +0000 (UTC) (envelope-from sunpoet@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id AC1B222FCE; Sat, 19 Dec 2020 20:04:02 +0000 (UTC) (envelope-from sunpoet@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id 0BJK42t5094633; Sat, 19 Dec 2020 20:04:02 GMT (envelope-from sunpoet@FreeBSD.org) Received: (from sunpoet@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id 0BJK41J3094629; Sat, 19 Dec 2020 20:04:01 GMT (envelope-from sunpoet@FreeBSD.org) Message-Id: <202012192004.0BJK41J3094629@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: sunpoet set sender to sunpoet@FreeBSD.org using -f From: Sunpoet Po-Chuan Hsieh Date: Sat, 19 Dec 2020 20:04:01 +0000 (UTC) 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 X-SVN-Group: ports-head X-SVN-Commit-Author: sunpoet X-SVN-Commit-Paths: in head/devel: . py-nest-asyncio X-SVN-Commit-Revision: 558474 X-SVN-Commit-Repository: ports MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-ports-head@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: SVN commit messages for the ports tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Dec 2020 20:04:03 -0000 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 +# $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 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