Skip to content

Use of the prefix pyiron_ #21

Draft
jan-janssen wants to merge 1 commit intomainfrom
pyiron
Draft

Use of the prefix pyiron_ #21
jan-janssen wants to merge 1 commit intomainfrom
pyiron

Conversation

@jan-janssen
Copy link
Copy Markdown
Member

The prefix pyiron_ should be used exclusively for the pyiron workflow engine and packages which depend on the pyiron workflow engine.

If the package pyiron_atomistics depends on pyiron_base and pyiron_lammps does not then it is confusing for our users why both packages use the prefix pyiron_. For the specific case of pyiron_lammps this was resolved by renaming it to lammpsparser.

Changes required in:

…ow engine and packages which depend on the pyiron workflow engine.

If the package `pyiron_atomistics` depends on `pyiron_base` and `pyiron_lammps` does not then it is confusing for our users why both packages use the prefix `pyiron_`. 
For the specific case of `pyiron_lammps` this was resolved by renaming it to `lammpsparser`. 

Changes required in:
- https://github.com/pyiron/pyiron_ontology - is archived 
- https://github.com/pyiron/pyiron_snippets - current discussion pyiron/pyiron_snippets#75
- https://github.com/pyiron/pyiron_vasp - suggested name vaspparser
- https://github.com/pyiron/pyiron_module_template - should be renamed to `module_template`
- https://github.com/pyiron/pyiron-publication-template - should be renamed to `publication-template`
@jan-janssen jan-janssen requested a review from liamhuber February 7, 2026 15:07
@jan-janssen jan-janssen marked this pull request as draft February 9, 2026 14:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant