Inconsistent tocoo/to_coo methods on different sparse types
Open
Nobody has claimed this yet.
bug
- Dominant language
- Python
- Stars
- 668
- Forks
- 141
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 4
Description
There is some inconsistencies in the naming of to-coo methods: GCXS has tocoo, DOK has to_coo. I assume to some extent it's to have some compatibility with scipy sparse. But then why not just have both methods on all types?
Contributor guide
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
Compare the GCXS tocoo and DOK to_coo methods and review the issue's compatibility concern with scipy sparse. Determine whether all sparse types should expose both names, then define the consistent API and verify the affected conversion methods across the sparse types.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100