-
Notifications
You must be signed in to change notification settings - Fork 25
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
qcportal 0.50 is incompatible with espaloma #185
Comments
qcportal 0.50 was released 6 days ago and has API-breaking changes. @mikemhenry : Can you help us update the We'll have to update to the new qcportal 0.50 API for releases beyond |
I tried to look for a |
@ijpulidos here is the new documentation, there are a ton of changes and new ways to access data, might be better to join the QCA call on Tuesdays for feedback from Ben and David. |
@chrisiacovella has been joining those calls---perhaps he would be in a good position to help fix this up? |
I can submit a repodata patch to add the pin since I think that will be faster than updating the API and then cutting a new release, but I do agree it would be better to update espaloma to work with the new qcportal. |
Looks like openff had the same issue conda-forge/conda-forge-repodata-patches-feedstock#550 |
Pinning to the old version is probably the best immediate fix (as syntax has completely changed, for the better, in the newest version). I'm currently working on putting essentially the same routines into model forge, so I can create a PR updating the syntax, including the much more efficient ways to fetch the records that have been introduced in the new code. |
Also in the meantime, adding |
Also update the recipe as well conda-forge/espaloma-feedstock#9 but that fix will not be retroactive like the repodata patch will be. |
Hi,
The new version of qcportal 0.50 is incompatible with the current espaloma package, may have to pin down to 0.15.8 or other in that line. It throws this error:
The text was updated successfully, but these errors were encountered: