-
Notifications
You must be signed in to change notification settings - Fork 96
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
Path to next atomate2 release #721
Comments
@janosh would you be ok to release a new pymatgen version? |
@utf sure, i'll take a look at custodian first though. i forgot why the release failed but it was on my todo list to fix |
Thank you! It's much appreciated. |
so it looks like the release failed because the |
Fantastic, thanks @janosh. |
This has now been done too. |
Brilliant thank you. We're just waiting on a new emmet-core release. |
Thanks for all your help. Atomate v0.0.14 has now been released. |
Currently we are stuck in dependency hell which is preventing a new release of atomate2. I've setup this issue to track the various PR's and dependency releases needed to get a new version out.
TransformedStructure.__getattr__
pymatgen#3617monty
version, allow newerpydantic
#720These are the essential fixes. If there are any other PRs people would like to prioritise for the next release then please let me know. Currently, I'm also tracking the following PRs which are less critical/should be mergeable once the above are completed:
KspacingMetalHandler
triggering on runs that don't useKSPACING
custodian#298KspacingMetalHandler
to VASP_DEFAULT_HANDLERS
#600In the meantime, it is recommended to install atomate2 with the strict dependency selection, which is guaranteed to give a working installation.
The text was updated successfully, but these errors were encountered: