Turn Scipy into a soft dependency
Open
Nobody has claimed this yet.
discussion
- Dominant language
- Python
- Stars
- 668
- Forks
- 141
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 4
Description
Right now, we are only using Scipy in:
dot/tensordot- Conversion to/from
scipy.sparse.spmatrixsubclasses.
Is it sensible keeping it as a hard dependency anymore?
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
Start by auditing the project's dependency configuration and the two SciPy use cases named in the issue: dot/tensordot and scipy.sparse.spmatrix conversion. Determine how optional imports and those conversions should behave without SciPy. Done means SciPy is no longer required for installation while the listed integrations remain supported when it is available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100