-
Notifications
You must be signed in to change notification settings - Fork 46
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
Resolve pomegranate import issues #701
base: main
Are you sure you want to change the base?
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #701 +/- ##
==========================================
+ Coverage 94.44% 94.93% +0.48%
==========================================
Files 106 106
Lines 4103 4103
==========================================
+ Hits 3875 3895 +20
+ Misses 228 208 -20
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
pomegranate_deps = ' '.join(minimum_pomegranate_versions) | ||
c.run(f'python -m pip install {install_deps}') | ||
c.run(f'python -m pip install --force-reinstall --no-cache-dir {pomegranate_deps}') |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
perhaps the pomegranate logic should only be run if minimum_pomegranate_versions
isn't empty
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That makes sense to me
This PR fixes #630 by switching to pomegranate 0.15 and updating the
BNLikelihood
andBNLogLikelihood
metrics to prompt the user to installpomegranate
viapip install sdmetrics[pomegranate]
instead ofpip install pomegranate
.pip install pomegranate
was installing pomegranate version 1.x which breaks the API we use, as seen in #642.