Skip to content

Dynamically wrap executorlib classes#726

Draft
liamhuber wants to merge 1 commit intomainfrom
dynamic_executorlib
Draft

Dynamically wrap executorlib classes#726
liamhuber wants to merge 1 commit intomainfrom
dynamic_executorlib

Conversation

@liamhuber
Copy link
Copy Markdown
Member

To dynamically create executorlib executors that use CacheOverride to be specific for pyiron_workflow. The hint is probably too generic, as we only expect this to even possibly work for base classes that leverage the file caching functionality.

A demo for #722

To dynamically `create executorlib` executors that use `CacheOverride` to be specific for `pyiron_workflow`. The hint is probably too generic, as we only expect this to even possibly work for base classes that leverage the file caching functionality.

Signed-off-by: liamhuber <liamhuber@greyhavensolutions.com>
@github-actions
Copy link
Copy Markdown

Binder 👈 Launch a binder notebook on branch pyiron/pyiron_workflow/dynamic_executorlib

@codecov
Copy link
Copy Markdown

codecov bot commented Jul 22, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 91.67%. Comparing base (9592209) to head (039413e).
⚠️ Report is 135 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #726      +/-   ##
==========================================
- Coverage   91.79%   91.67%   -0.12%     
==========================================
  Files          34       34              
  Lines        3730     3737       +7     
==========================================
+ Hits         3424     3426       +2     
- Misses        306      311       +5     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@stale
Copy link
Copy Markdown

stale bot commented Feb 12, 2026

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Feb 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant