-
Notifications
You must be signed in to change notification settings - Fork 874
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
Conversation
into sub-modules
In favor, thanks @janosh! The |
e3fbc67
to
41e6d99
Compare
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. |
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. |
follow up PR to #3835, specifically this exchange, that splits VASP input sets (currently all in a 3.3k line
sets.py
file) into submodulesbase.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
inbase.py
since they were already marked private and no other files in pymatgen were importing thempinging @shyuep, @mkhorton, @esoteric-ephemera, @utf, @JaGeo for review