| Commit History - (may be incomplete: for full details, see links to repositories near top of page) |
| Commit | Credits | Log message |
1.5.0 25 Dec 2024 19:15:19
    |
Po-Chuan Hsieh (sunpoet)  |
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/master |
1.4.0_1 08 Apr 2024 06:45:42
    |
Po-Chuan Hsieh (sunpoet)  |
devel/py-aiorwlock: Convert to USE_PYTHON=pep517
- Bump PORTREVISION for package change |
1.4.0 21 Feb 2024 15:07:11
    |
Po-Chuan Hsieh (sunpoet)  |
devel/py-aiorwlock: Update to 1.4.0
Changes: https://github.com/aio-libs/aiorwlock/releases |
1.3.0 09 Jul 2023 10:10:21
    |
Po-Chuan Hsieh (sunpoet)  |
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. |