-
Notifications
You must be signed in to change notification settings - Fork 868
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
Breaking behavior: Removal of pymatgen.io.vasp.sets.get_vasprun_outcar
without warning
#3988
Comments
This has been fixed with the 2024.8.9 emergency release. |
Thank you! |
pymatgen.io.vasp.sets.get_vasp_outcar
without warningpymatgen.io.vasp.sets.get_vasprun_outcar
without warning
@shyuep please unrevert my #3865 PR. just add back the the split of several-thousand-line files is an obvious improvement. you're throwing away my time by undoing that work
what's that supposed to mean? there are hundreds of PRs that you don't agree to. if every one of those required your explicit approval, pymatgen development would grind to a standstill |
I think we should re-open #3865 and more comprehensively test. It's a good idea to split these files up for maintainability. This can be done without backwards-incompatible changes; it seems like However, I would go further than #3865. The To be specific |
Python version
3.11
Pymatgen version
pymatgen 2024.8.8
Operating system version
No response
Current behavior
The above used to work on pymatgen < 2024.8.8 but does not exist any longer in pymatgen >= 2024.8.8. I don't believe there was a deprecation warning, so it may break other people's codes as-is.
Expected Behavior
A deprecation warning before removal.
Minimal example
No response
Relevant files to reproduce this bug
No response
The text was updated successfully, but these errors were encountered: