Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Feature] Serialise executors

Open
#260 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python

Research direction

Start with the Executors in pympipool and trace how they use zmq to connect to the function-executing process. Investigate what executor state must be stored, how already-submitted messages behave across deserialization, and whether the executor or function process owns the server. Done means these lifecycle questions have a defined serialization design.

Written by the indexing model from the issue text.

Description

enhancement

As the Executors in pympipool typically use zmq to connect the executor to the process which is executing the functions it should in principle be possible to serialise the executor - store the information of the executor - and then deserialise the same object again. Still it is not clear what happens to the messages already submitted and in addition it is also not clear if the server process is started by the executor or by the process executing the python functions.

Dominant language
Python
Stars
77
Forks
7
Avg merge
10h 32m
Merged PRs (30d)
12

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from pyiron/executorlib

All issues in pyiron/executorlib

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.