pyiron / pyiron/pyiron_database
Make pyiron_database independent of pyiron_workflow
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
As we are trying to decouple individual components of pyiron, I would suggest to use the dictionary format discussed here
Contributor guide
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 reading the dictionary format discussed in pyiron_workflow issue 576 and compare it with pyiron_database's current dependency on pyiron_workflow. The work is complete when pyiron_database is independent of pyiron_workflow while using the agreed dictionary format; no specific files or tests are identified in this issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- database
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100