microsoft / microsoft/component-detection
Investigate `--no-compile` with PipReport detector
Open
Nobody has claimed this yet.
detector:pip
good first issue
status:ready
type:refactor
- Dominant language
- C#
- Stars
- 553
- Forks
- 135
- Avg merge
- 20h 58m
- Merged PRs (30d)
- 6
Description
A potential improvement for the PipReport detector is to see if `--no-compile` produces any benefit to performance when used in conjunction with the other existing parameters. Validate that the dependency graph is still the same and that there is a notable improvement in detection time.
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 locating the PipReport detector and its existing parameters, then benchmark detection with and without --no-compile. Compare the resulting dependency graphs and detection times; the investigation is done when it establishes whether the graph remains unchanged and whether the performance improvement is notable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, python
- Domain
- devtools, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100