| Port details |
- py-aiorwlock Read write lock for asyncio
- 1.5.0 devel
 =2      1.4.0_1Version of this port present on the latest quarterly branch. - Maintainer: sunpoet@FreeBSD.org
- Port Added: 2023-07-09 10:36:34
- Last Update: 2024-12-25 19:15:19
- Commit Hash: b44c4e5
- People watching this port, also watch:: jdictionary, py311-Automat, py311-python-gdsii, py39-PyOpenGL, p5-Sane
- Also Listed In: python
- License: APACHE20
- WWW:
- https://github.com/aio-libs/aiorwlock
- Description:
- 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.
  ¦  ¦  ¦  ¦ 
- Manual pages:
- FreshPorts has no man page information for this port.
- pkg-plist: as obtained via:
make generate-plist - There is no configure plist information for this port.
- Dependency lines:
-
- ${PYTHON_PKGNAMEPREFIX}aiorwlock>0:devel/py-aiorwlock@${PY_FLAVOR}
- To install the port:
- cd /usr/ports/devel/py-aiorwlock/ && make install clean
- To add the package, run one of these commands:
- pkg install devel/py-aiorwlock
- pkg install py311-aiorwlock
NOTE: If this package has multiple flavors (see below), then use one of them instead of the name specified above.
NOTE: This is a Python port. Instead of py311-aiorwlock listed in the above command, you can pick from the names under the Packages section.- PKGNAME: py311-aiorwlock
- Package flavors (<flavor>: <package>)
- distinfo:
- TIMESTAMP = 1734888152
SHA256 (aiorwlock-1.5.0.tar.gz) = b529da24da659bdedcf68faf216595bde00db228c905197ac554773620e7fd2f
SIZE (aiorwlock-1.5.0.tar.gz) = 7315
Packages (timestamps in pop-ups are UTC):
- Dependencies
- NOTE: FreshPorts displays only information on required and default dependencies. Optional dependencies are not covered.
- Build dependencies:
-
- py311-poetry-core>=1.0.0 : devel/py-poetry-core@py311
- python3.11 : lang/python311
- py311-build>=0 : devel/py-build@py311
- py311-installer>=0 : devel/py-installer@py311
- Test dependencies:
-
- python3.11 : lang/python311
- Runtime dependencies:
-
- python3.11 : lang/python311
- This port is required by:
- for Run
-
Deleted ports which required this port:
- * - deleted ports are only shown under the This port is required by section. It was harder to do for the Required section. Perhaps later...
Configuration Options:- No options to configure
- Options name:
- devel_py-aiorwlock
- USES:
- python
- FreshPorts was unable to extract/find any pkg message
- Master Sites:
|
| 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. |
As an Amazon Associate I earn from qualifying purchases.