pyiron/pyiron_workflow

Add convenient callbacks for graph managers

Open

#612 opened on Mar 5, 2025

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Python (3 forks)auto 404
enhancementgood first issue

Repository metrics

Stars
 (23 stars)
PR merge metrics
 (PR metrics pending)

Description

E.g. for pyironflow it would actually probably be quite nice to add

finally:
    for fnc in self.child_starting/finished/emitting_callbacks:
        fnc(child)

in each of Composite.register_child_starting/finished/emitting, where the callbacks take the form Callable[[Node], None] and the properties child_starting/finished/emitting_callbacks default to an empty list.

Contributor guide

Research direction
Add child starting callbacks, child finished callbacks, child emitting callbacks properties (defaulting to empty lists) to Composite. In Composite.register child starting/finished/emitting, after the main logic, iterate over the corresponding callback list and call each callback with the child node. Ensure callbacks are callables (Callable[[Node], None]).
Tech stack
python
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Python
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60