Closed nsheff closed 1 year ago
I think just a reminder to update peppy requirement at release.
@nsheff do you have an example of a refgenie
build command which triggered this error? I'd like to at least test locally and perhaps also add a test that would fail now but then succeed with a version bump of the peppy
dependency.
Probably we should just make the next version of looper rely on the latest version of peppy, since we'll be making other changes, and then there's no need to track this down.
Since I ran into this 2 years ago, I am not sure if it's even a problem anymore.
Closing in favor of #346
Using dev version of looper and running refgenie builds, I get:
ImportError: cannot import name 'make_abs_via_cfg' from 'peppy.utils'
does it rely on a version of peppy that is not specified?