Investigate `complex` dtype failure.
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 668
- Forks
- 141
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 4
Description
I wonder about this weird issue in Python 3.11 that occurs sometimes for complex dtype...
Originally posted by @mtsokol in https://github.com/pydata/sparse/issues/815#issuecomment-2503534924
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
No file, test, or entry point is named. Start by reproducing the reported complex-dtype failure under Python 3.11 and narrow down when it occurs in the sparse array workflow. Done means the failure is characterized and its cause or a reproducible test case is recorded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100