-
Notifications
You must be signed in to change notification settings - Fork 76
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
[question] How to import string_grouper_utils? #61
Comments
from string_grouper_utils import new_group_rep_by_highest_weight, \
new_group_rep_by_earliest_timestamp, new_group_rep_by_completeness (As detailed in this link.) |
@ParticularMiner thanks for the input. I tried that, but received this error: Somehow string_grouper works, but string_grouper_utils cannot be found |
You are right. It seems you've discovered a bug as I'm also able to reproduce this error. I'm not sure how this bug crept in, since it has always worked before. Perhaps this is due to a recent upgrade of pip. Anyway I've also found a fix for this but I'm not sure how long it will take to reach the main branch. If you are willing to download the package files from GitHub instead of pypi.org then I could help you. Let me know if you are willing then I'll direct you to the relevant branch. Otherwise you'd have to wait until string_grouper is updated on pypi.org and that could take a while. Meanwhile, many thanks for bringing this to our attention! |
Okay, great. Thanks for the quick feedback. I'll download it directly from Github, no problem. Which branch should I refer to? |
The branch can be found at this link.
pip install . This should install string_grouper in the same location where your other python packages are. Kindly let me know afterwards if this solves your problem. Cheers! |
Hi all, I think this is a very simple question, but how can one import the string_grouper_utils module? I've installed string_grouper via pip install, but cannot seem to access the modules within string_grouper_utils, such as new_group_rep_by_highest_weight. Anyone?
The text was updated successfully, but these errors were encountered: