Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Split VASP input sets into submodules #3865

Merged
merged 8 commits into from
Aug 7, 2024
Merged

Split VASP input sets into submodules #3865

merged 8 commits into from
Aug 7, 2024

Conversation

janosh
Copy link
Member

@janosh janosh commented Jun 5, 2024

follow up PR to #3835, specifically this exchange, that splits VASP input sets (currently all in a 3.3k line sets.py file) into submodules base.py, lobster.py, matpes.py, mit.py, mp.py, mvl.py.

no breaking changes expected as all input sets are re-exported from the new pymatgen/io/vasp/sets/__init__.py and so are importable the same way they were before. i did not re-export some private functions like _get_recommended_lreal in base.py since they were already marked private and no other files in pymatgen were importing them

pinging @shyuep, @mkhorton, @esoteric-ephemera, @utf, @JaGeo for review

@janosh janosh added io Input/output functionality vasp Vienna Ab initio Simulation Package dx Developer experience labels Jun 5, 2024
@janosh janosh requested review from shyuep and mkhorton as code owners June 5, 2024 22:51
@DanielYang59
Copy link
Contributor

Ah there would be a million merge conflicts for #3863 😭

I don't have any objection for this PR, but could we "possibly" split from #3863? As I think splitting would be easier (cut and paste) than reapplying all changes?

@mkhorton
Copy link
Member

mkhorton commented Jun 9, 2024

In favor, thanks @janosh! The sets.py file was getting far too unwieldly.

@janosh janosh force-pushed the master branch 2 times, most recently from e3fbc67 to 41e6d99 Compare August 3, 2024 19:01
@janosh janosh enabled auto-merge (squash) August 7, 2024 17:41
@janosh janosh merged commit 81b802e into master Aug 7, 2024
35 checks passed
@janosh janosh deleted the split-vasp-sets branch August 7, 2024 18:54
janosh added a commit that referenced this pull request Aug 7, 2024
should have been deleted in #3865 but was missed due to the migration to src layout copying  src/pymatgen/io/vasp/sets.py to a new location after #3865 was opened
@janosh janosh added the housekeeping Moving around or cleaning up old code/files label Aug 9, 2024
shyuep added a commit that referenced this pull request Aug 9, 2024
shyuep added a commit that referenced this pull request Aug 9, 2024
@shyuep
Copy link
Member

shyuep commented Aug 9, 2024

Given that I expressed my objections to the split earlier, this PR should not have been merged without my review. Also, this PR clearly broke something. See #3988. I have reverted this PR. I will reiterate that these kind of PRs need to be consulted on. I do not want to have to deal with unnecessary complaints of backwards incompatibility.

@shyuep
Copy link
Member

shyuep commented Aug 9, 2024

Further, I have no idea how this PR was done, but the PR changes showed the creation of the sets folder with the submodules, but it did not show the deletion of the sets.py file. As a result, reversion of this PR caused all kinds of breakages.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dx Developer experience housekeeping Moving around or cleaning up old code/files io Input/output functionality vasp Vienna Ab initio Simulation Package
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants