Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Investigate --no-compile with PipReport detector #1149

Open
cobya opened this issue Jun 4, 2024 · 1 comment
Open

Investigate --no-compile with PipReport detector #1149

cobya opened this issue Jun 4, 2024 · 1 comment
Labels
detector:pip The pip detector good first issue Good for newcomers status:ready Ready to start implementation type:refactor Refactoring or improving of existing code

Comments

@cobya
Copy link
Contributor

cobya commented Jun 4, 2024

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.
@cobya cobya added detector:pip The pip detector status:ready Ready to start implementation type:refactor Refactoring or improving of existing code good first issue Good for newcomers labels Jun 4, 2024
@cobya
Copy link
Contributor Author

cobya commented Jun 6, 2024

From limited local testing, this seems to have no effect on report generation times. I'll try and investigate further later on.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
detector:pip The pip detector good first issue Good for newcomers status:ready Ready to start implementation type:refactor Refactoring or improving of existing code
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@cobya