Open pavankum opened 9 months ago
qcportal 0.50 was released 6 days ago and has API-breaking changes.
@mikemhenry : Can you help us update the espaloma
conda package to pin to 0.15.8?
We'll have to update to the new qcportal 0.50 API for releases beyond espaloma
0.3 since the paper is imminent.
I tried to look for a CHANGELOG
(or similar) but I couldn't easily find one, do we know if there's documentation on what was changed? Just such that it's easier to know what to adapt on our end, if possible. I know the qcportal
package is now being developed inside the qcfractal
repo.
@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 https://github.com/conda-forge/conda-forge-repodata-patches-feedstock/pull/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 "qcportal<0.50.0a0"
when installing espaloma will work.
Also update the recipe as well https://github.com/conda-forge/espaloma-feedstock/pull/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: