inducer / inducer/arraycontext
Loopy a hard dependency?
- Dominant language
- Python
- Stars
- 9
- Forks
- 11
- Avg merge
- 17h 12m
- Merged PRs (30d)
- 2
Description
Is there a specific reason why Loopy should be a hard dependency[^1]? My understanding was `transform_loopy_program` will get kicked in only when the implementation demands.
Thanks!
[^1]: https://github.com/inducer/arraycontext/blob/main/setup.py#L46
Contributor guide
No contributing guide indexed for this repository
Research direction
Inspect setup.py at the dependency declaration around line 46 and trace where transform_loopy_program is used. Determine whether Loopy is required during normal installation or only for that implementation path; the issue is done when the dependency behavior matches the documented intent and the relevant installation or usage checks pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100