devel/py-aiorwlock: Update to 1.5.1 Changes: https://github.com/aio-libs/aiorwlock/releases97f771f152
Port details
devel/py-aiorwlock 1.5.1
Read write lock for asyncio
- Maintainer
- sunpoet@FreeBSD.org
- Packages
- latest: 1.5.1
- Upstream
- up to date
- Last update
- to 1.5.1 · 97f771f152
- Quarterly
- 2026Q4: 1.5.1
- WWW
- https://github.com/aio-libs/aiorwlock
- Links
- cgit · VuXML
Unaddressed and VuXML only (0)
No unaddressed CVE and nothing reported by
pkg audit for the packaged version 1.5.1.Fixed (0)
No VuXML entries for this package.
Problem reports (0) · open in Bugzilla, most recently changed first
None.
Commits (5)
devel/py-aiorwlock: Update to 1.5.0 Changes: https://github.com/aio-libs/aiorwlock/releases https://github.com/aio-libs/aiorwlock/blob/master/CHANGES.rst https://github.com/aio-libs/aiorwlock/commits/masterb44c4e5e45
devel/py-aiorwlock: Convert to USE_PYTHON=pep517 - Bump PORTREVISION for package changed1890bbade
devel/py-aiorwlock: Update to 1.4.0 Changes: https://github.com/aio-libs/aiorwlock/releases076915b967
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.c6a13c6a83