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

[Documentation] Place a yield statement in the init function

Open
#430 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

The issue does not name a file, test, or specific entry point beyond the init function. First locate that function and understand how input values are created and how output is gathered; done should include an agreed yield-based design that supports creating only required inputs and overwriting corresponding entries.

Written by the indexing model from the issue text.

Description

documentation

Rather than creating all input values at once this would allow to create only the required input values and overwrite the corresponding entries afterwards. Still it might be difficult as we anyway plan to gather all the output at the end.

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.