From nobody Sun Jul 9 10:33:26 2023 X-Original-To: dev-commits-ports-all@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4QzNlB5TGJz4lk3Z; Sun, 9 Jul 2023 10:33:26 +0000 (UTC) (envelope-from git@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 "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QzNlB4hbLz3t83; Sun, 9 Jul 2023 10:33:26 +0000 (UTC) (envelope-from git@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1688898806; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=RdIHcVQUqKUs6kksgmtyzPu6gUyvX1eyiXExGwTX/RY=; b=SaCGc2tNZtdTnEkze4J70CcZiqd2A969GCANnD63qcWFvFAOQ9Hlk4etFtJDYnBstN+6CZ j9pKnDa6UYLvOYYOnK7zmLwTLatiFBjXOJBM1qzecvSwadtFJU2Xz1aYS2HwNabAyUGQAs Rwr3dgNv2YzOrEZNkmB1y81doWfA/APJzvw2z5CtXSz0aFp3OjqZuGyBypicR3t5uE+oz6 Z3vt9LVpNOZM3WxnOt+V3mo8tUR56tSfCNHyfuJU5yjP37S+9t4iK4DU5onpXH7JCLkHab lVm73/x4VWL+vg1GZjdpUHME+hf+B74yqc62aQPQfNaI9gFQvcgkmz2Wn27gKQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1688898806; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=RdIHcVQUqKUs6kksgmtyzPu6gUyvX1eyiXExGwTX/RY=; b=Nrt0vgnGEBxByLTkN/DPqHcc9NkCZnf+u2ITa1EKQVGhgTsol+aOYz9+lLeLnrQxRc6dHv 6SWu2i9rcYRm+13GBHiiB6e/1M+9bZ4qVZoNWsDCYAs/L28H/ga0mGJvQw6ixudcdJVcbN fti6/OSDRdCX3vxFl399umI4BoEu6QJLQKL3Ni11Z3RtlkNc3mc19/rsErw0p1nqZ65snq qzNwENM7W6ZcXxAR2Z3AgUXizZRMNHckzAFRhL7aCXUl1851+2R9K0nN8WUyy/xG6fBlAg gmVWmrV2Gn55PAjRX/Y3YXX1PRWy4kMxS2gkbs7qi4VzIdUycMmUnxyY8uGXsg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1688898806; a=rsa-sha256; cv=none; b=JiqrJrg8HooLTXQ94jg2Ns89e0Km/aoHlFKdB6vzF6bvV1GBAiZ7JwdZ+gt17pdMM4tvRU pz3VED581y17ZqqSd21xu+mlbwXoBpQoBmCAuFmAxVayINNVoLge80vKmFfytmCvgGKX/p lE0snGhgqWWGCm4oCeOkHYOu6arBRYHqxd9nG+PykmX4AcMITRiGhXylYGg9ExMamf3h4q P+o3Oc5EprjZcZ4d0leApfmxABK/dlPaAGtZzXYQ5sbEtLXkx5wf9BcKgNZ3023KICeifS u10AcbTWNp2Xbf7EwlvCYUMtrUc0r5zCIJgUNcy8/vk3sm0kw1bzK7tGWSKogA== Received: from gitrepo.freebsd.org (gitrepo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:5]) (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 did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4QzNlB3d37z10C4; Sun, 9 Jul 2023 10:33:26 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org ([127.0.1.44]) by gitrepo.freebsd.org (8.17.1/8.17.1) with ESMTP id 369AXQ3b055095; Sun, 9 Jul 2023 10:33:26 GMT (envelope-from git@gitrepo.freebsd.org) Received: (from git@localhost) by gitrepo.freebsd.org (8.17.1/8.17.1/Submit) id 369AXQqG055094; Sun, 9 Jul 2023 10:33:26 GMT (envelope-from git) Date: Sun, 9 Jul 2023 10:33:26 GMT Message-Id: <202307091033.369AXQqG055094@gitrepo.freebsd.org> To: ports-committers@FreeBSD.org, dev-commits-ports-all@FreeBSD.org, dev-commits-ports-main@FreeBSD.org From: Po-Chuan Hsieh Subject: git: c6a13c6a8342 - main - devel/py-aiorwlock: Add py-aiorwlock 1.3.0 List-Id: Commit messages for all branches of the ports repository List-Archive: https://lists.freebsd.org/archives/dev-commits-ports-all List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-dev-commits-ports-all@freebsd.org X-BeenThere: dev-commits-ports-all@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Git-Committer: sunpoet X-Git-Repository: ports X-Git-Refname: refs/heads/main X-Git-Reftype: branch X-Git-Commit: c6a13c6a8342ee029b240ece46013d5792d78d9a Auto-Submitted: auto-generated X-ThisMailContainsUnwantedMimeParts: N The branch main has been updated by sunpoet: URL: https://cgit.FreeBSD.org/ports/commit/?id=c6a13c6a8342ee029b240ece46013d5792d78d9a commit c6a13c6a8342ee029b240ece46013d5792d78d9a Author: Po-Chuan Hsieh AuthorDate: 2023-07-09 10:10:21 +0000 Commit: Po-Chuan Hsieh CommitDate: 2023-07-09 10:10:21 +0000 devel/py-aiorwlock: Add py-aiorwlock 1.3.0 aiorwlock provides read write lock for asyncio . A RWLock maintains a pair of associated locks, one for read-only operations and one for writing. The read lock may be held simultaneously by multiple reader tasks, so long as there are no writers. The write lock is exclusive. Whether or not a read-write lock will improve performance over the use of a mutual exclusion lock depends on the frequency that the data is read compared to being modified. For example, a collection that is initially populated with data and thereafter infrequently modified, while being frequently searched is an ideal candidate for the use of a read-write lock. However, if updates become frequent then the data spends most of its time being exclusively locked and there is little, if any increase in concurrency. --- devel/Makefile | 1 + devel/py-aiorwlock/Makefile | 19 +++++++++++++++++++ devel/py-aiorwlock/distinfo | 3 +++ devel/py-aiorwlock/pkg-descr | 12 ++++++++++++ 4 files changed, 35 insertions(+) diff --git a/devel/Makefile b/devel/Makefile index 656d457e4d40..efebea912f3e 100644 --- a/devel/Makefile +++ b/devel/Makefile @@ -4197,6 +4197,7 @@ SUBDIR += py-aiologger SUBDIR += py-aiorpcX SUBDIR += py-aiortc + SUBDIR += py-aiorwlock SUBDIR += py-aiosignal SUBDIR += py-airtable-python-wrapper SUBDIR += py-amalgamate diff --git a/devel/py-aiorwlock/Makefile b/devel/py-aiorwlock/Makefile new file mode 100644 index 000000000000..7f44ce2eaba7 --- /dev/null +++ b/devel/py-aiorwlock/Makefile @@ -0,0 +1,19 @@ +PORTNAME= aiorwlock +PORTVERSION= 1.3.0 +CATEGORIES= devel python +MASTER_SITES= PYPI +PKGNAMEPREFIX= ${PYTHON_PKGNAMEPREFIX} + +MAINTAINER= sunpoet@FreeBSD.org +COMMENT= Read write lock for asyncio +WWW= https://github.com/aio-libs/aiorwlock + +LICENSE= APACHE20 +LICENSE_FILE= ${WRKSRC}/LICENSE + +USES= python +USE_PYTHON= autoplist concurrent distutils + +NO_ARCH= yes + +.include diff --git a/devel/py-aiorwlock/distinfo b/devel/py-aiorwlock/distinfo new file mode 100644 index 000000000000..390a6f28add9 --- /dev/null +++ b/devel/py-aiorwlock/distinfo @@ -0,0 +1,3 @@ +TIMESTAMP = 1688166002 +SHA256 (aiorwlock-1.3.0.tar.gz) = 83f12d87df4b9728a0b8fda1756585ab0d652b107bab59c6084e1b1ad692ab45 +SIZE (aiorwlock-1.3.0.tar.gz) = 12945 diff --git a/devel/py-aiorwlock/pkg-descr b/devel/py-aiorwlock/pkg-descr new file mode 100644 index 000000000000..7a954b551982 --- /dev/null +++ b/devel/py-aiorwlock/pkg-descr @@ -0,0 +1,12 @@ +aiorwlock provides read write lock for asyncio . A RWLock maintains a pair of +associated locks, one for read-only operations and one for writing. The read +lock may be held simultaneously by multiple reader tasks, so long as there are +no writers. The write lock is exclusive. + +Whether or not a read-write lock will improve performance over the use of a +mutual exclusion lock depends on the frequency that the data is read compared to +being modified. For example, a collection that is initially populated with data +and thereafter infrequently modified, while being frequently searched is an +ideal candidate for the use of a read-write lock. However, if updates become +frequent then the data spends most of its time being exclusively locked and +there is little, if any increase in concurrency.