[Documentation] Users of executorlib
Open
Nobody has claimed this yet.
documentation
- Dominant language
- Python
- Stars
- 77
- Forks
- 7
- Avg merge
- 10h 32m
- Merged PRs (30d)
- 12
Description
I guess it is helpful to collect examples of how executorlib is used in other projects:
Executors
- https://github.com/pyiron/pylammpsmpi/pull/371 -
pylammpsmpiis currently transitioning to use executorlib Executors - https://github.com/pyiron/pyiron_base - is using executorlib Executors
- https://github.com/pyiron/pyiron_workflow/pull/678 -
pyiron_workflowis using executorlib Executors
Prototypes using executors
- https://github.com/pyiron-dev/pipefunc-executorlib
- https://github.com/pyiron-dev/executorlib-emcee
- https://github.com/pyiron-dev/executorlib-omp4py
Custom Spawners
- https://github.com/pyiron/conda_subprocess/pull/144 -
conda_subprocessdefines it is own executorlib Spawner
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the repository documentation or examples index where usage references belong. Organize the listed executor, prototype, and custom-spawner projects into the relevant documentation section, preserving their links and descriptions. Done means the examples are easy to find and all projects named in the issue are represented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100