Candidates are not used in 0.6.0.
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 4.2k
- Forks
- 385
- PR merge metrics
- No merged PRs in 30d
Description
Hi!
I would like to first thank the authors for the incredibly useful package!
I updated my env from 0.5.1 to 0.6.0 and noticed that now candidates to keywords, that I pass in the function model.extract_keywords is not used. So, I always get keywords from CountVectorizer instead. Could you please, check that?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at model.extract_keywords and compare how the candidates argument is handled between versions 0.5.1 and 0.6.0. Check why CountVectorizer results replace the supplied candidates, then verify that passing candidates produces keywords from that set rather than from CountVectorizer.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, scikit-learn
- Domain
- machine-learning
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100