Python multiprocessing-intenum
IntEnumValue is an implementation of a multiprocessing safe shared object
for IntEnum enum values.
The IntEnumValue appears and can be used much like an IntEnum, while
internally, it uses a multiprocessing.Value shared ctypes integer object
to store the integer value of the enum in a multiprocessing safe way.
It is fully typed and implemented as a generic class, thus allowing to guard
against programming errors where values other than the designated
specific IntEnum type are being assigned.
License
Copyright (C) 2024-2026 credativ GmbH https://www.credativ.de/en/
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
Installation
- Install required packages, e.g. on Debian GNU/Linux:
apt-get install git python3
-
Install uv from https://github.com/astral-sh/uv/releases
-
Setup and activate Python virtual environment:
uv venv --prompt='mp-intenum' . .venv/bin/activate -
Install Python requirements in the virtual environment:
uv sync --locked -
Build:
make dist
Development
- Run code quality checks:
make lint
- Run test suite:
make test
Usage
Example
To illustrate the usage, an example of a multithreaded worker is used, which has an internal state represented as an enum that should be tracked across its threads.
To use a multiprocessing safe IntEnum, first define the actual underlying
IntEnum type:
class WorkerStatusEnum(IntEnum):
UNAVAILABLE = enum.auto()
IDLE = enum.auto()
CALCULATING = enum.auto()
IntEnumValue is a generic class, accepting a type parameter for the type
of the underlying IntEnum.
Thus define the corresponding IntEnumValue type for that IntEnum like
this:
class WorkerStatus(IntEnumValue[WorkerStatusEnum]):
pass
Now this WorkerStatus type can be used like an enum to track the state:
>>> status = WorkerStatus(WorkerStatusEnum.IDLE)
>>> status.name
'IDLE'
>>> status.value
2
>>> with status.get_lock():
... status.set(WorkerStatusEnum.CALCULATING)
>>> status.name
'CALCULATING'
>>> status.value
3
It can, of course, also be wrapped in a dedicated class, which the remaining examples will further expand on:
class WorkerState:
def __init__(self) -> None:
self.status = WorkerStatus(WorkerStatusEnum.IDLE)
When using multiple multiprocessing.Value instances (including
IntEnumValue ones) that should share a lock to allow ensuring that they
can only be changed in a consistent state, pass that shared lock as a
keyword argument on instantiation:
class WorkerState:
def __init__(self) -> None:
self.lock = multiprocessing.RLock()
self.status = WorkerStatus(WorkerStatusEnum.IDLE, lock=self.lock)
self.job_id = multiprocessing.Value("i", -1, lock=self.lock)
def get_lock(self) -> Lock | RLock:
return self.lock
To avoid having to call the set() method to assign a value to the
IntEnumValue attribute, it is suggested to keep the actual
attribute private to the class and implement getter and setter methods for a
public property that hides this implementation detail, e.g. as follows:
class WorkerState:
def __init__(self) -> None:
self._status = WorkerStatus(WorkerStatusEnum.IDLE)
@property
def status(self) -> WorkerStatusEnum:
return self._status # type: ignore[return-value]
@status.setter
def status(self, status: WorkerStatusEnum | str) -> None:
self._status.set(status)
This can be used in a more elegant manner by simply assigning to the status attribute:
>>> state = WorkerState()
>>> state.status.name
'IDLE'
>>> with state.get_lock():
... state.status = WorkerStatusEnum.CALCULATING
>>> state.status.name
'CALCULATING'
The specific IntEnumValue type can override methods to add further
functionality.
A common example is overriding the set() method to add logging:
class WorkerStatus(IntEnumValue[WorkerStatusEnum]):
def set(self, value: WorkerStatusEnum | str) -> None:
super().set(value)
logger.info(f"WorkerStatus set to '{self.name}'")
Metadata
Release files for multiprocessing-intenum 1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| multiprocessing_intenum-1.1.tar.gz | 22.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| multiprocessing_intenum-1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 32.8 kB
Release files / multiprocessing_intenum-1.1.tar.gz
| Download URL | multiprocessing_intenum-1.1.tar.gz |
|---|---|
| Size | 22.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f6012dfbc8d751f219a4dc786ffc4b558089c1440c3836046a4fb4a1884c67e5
|
|
BLAKE2b-256 checksum How to use checksums |
023e04a289223858f46be212c35db119dd746299b3129026ef937c7f6cead3a6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 1, 2026.
Transparency logRelease files / multiprocessing_intenum-1.1-py3-none-any.whl
| Download URL | multiprocessing_intenum-1.1-py3-none-any.whl |
|---|---|
| Size | 10.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6d3d6330110a09559c827ff3757f3e0b6f104149944486eb278d4210525fd7e1
|
|
BLAKE2b-256 checksum How to use checksums |
a056f8e2fd5542a85a1563571e427399149c4e02f6c6e6f5b9d140d2dd11eebf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 1, 2026.
Transparency log